SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for int35.ui.dev.wbsrvc.com, int40.ui.dev.wbsrvc.com, maxliving-webhooks.staging.wbsrvc.com, maxliving-webhooks.wbsrvc.com, phishing.wbsrvc.com, relay.wbsrvc.com, sapi.wbsrvc.com, not for md02.com
Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
CN=sapi.wbsrvc.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
October 29, 2025
Valid Until
January 27, 2026
9 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8A:6D:79:20:8F:21:4E:B8:27:14:70:D3:25:20:AD:16:20:7B:CF:96:10:FB:B2:FD:16:9B:AF:9A:36:D4:B5:7F
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=60
Content-Security-Policy
Good
default-src; script-src; style-src; +10 more
default-src 'self'; script-src 'self' 'sha256-ETWJMGu3Enj4jG4CFECxfP2c3Do3HPOoIGX3RuqSk4E=' 'sha256-UNSjrBN573Gq5WKBQX8pe6R5RxDXbRjK1TIF7JnDtRI=' 'sha256-jsM15EgcnljVkAqUSwvhK2zpKO95FVxVXa/KCLMxHP0=' https://www.gstatic.com https://www.google.com https://ph.cake.io https://use.typekit.net ; style-src 'report-sample' 'self' 'unsafe-inline' https://fonts.googleapis.com; object-src 'self' *; base-uri 'self'; connect-src 'self'; font-src 'self' https://fonts.gstatic.com https://use.typekit.net; frame-ancestors *; frame-src 'self' https://www.google.com; img-src * ; manifest-src 'self'; media-src 'self'; worker-src 'none';
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance