Open Cached · just now
86/100 SECURITY SCORE

Certificate Information

Subject
CN=portswigger.net
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
April 01, 2025
Valid Until
April 30, 2026 178 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DB:94:AC:B8:AD:F5:93:37:E7:B0:19:A6:B3:78:85:86:CF:F8:7E:02:A6:FD:07:08:6C:FD:B8:F2:E9:66:CA:D2
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=31536000; preload
Content-Security-Policy
Strong
default-src; form-action; base-uri; +8 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Add X-Content-Type-Options: nosniff
  • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Not Authorized (Potential misconfiguration)
Incident Reporting
CAA Issues
  • CRITICAL: Current certificate issuer 'C=US, O=Amazon, CN=Amazon RSA 2048 M02' is NOT authorized by CAA records. Authorized CAs: comodoca.com, letsencrypt.org, pki.goog, awstrust.com
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • You have authorized 4 CAs - consider limiting to only the CAs you actively use
  • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain