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 quora.com, *.quora.com, *.www.quora.com, *.tch.quora.com, *.tch.www.quora.com, qr.ae, *.qr.ae, fs.quoracdn.net, *.fs.quoracdn.net, not for quoracdn.net
Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=quora.com
Issuer
C=US, O=Google Trust Services, CN=WR1
Valid From
March 31, 2026
Valid Until
June 29, 2026
78 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
72:D2:07:6D:77:8D:14:5C:76:8D:A8:E8:B7:4B:1B:21:72:9F:BC:4D:C4:C1:77:F1:7A:0B:0C:30:1C:46:3A:5A
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
accelerometer=(), browsing-topics=(), camera=(); +14 more
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
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
Subject Alternative Names
11 domains
cf2.quoracdn.net
fs.quoracdn.net
*.cf2.quoracdn.net
*.fs.quoracdn.net
qr.ae
*.qr.ae
quora.com
*.quora.com
*.tch.quora.com
*.tch.www.quora.com
*.www.quora.com
Other domains in certificate