Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=content.as207960.net
Issuer
C=US, O=Google Trust Services, CN=WR1
Valid From
August 11, 2026
Valid Until
November 09, 2026 67 days
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
43:2D:FF:44:5C:1A:BE:55:A8:A1:53:81:E6:41:E8:FF:EE:4D:24:26:5A:CD:13:C8:87:5E:70:DF:96:76:EF:48
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • 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
Authorized (Matches CAA policy)
Authorized CAs
pki.goog ; accounturi=https://dv.acme-v02.api.pki.goog/account/s0zLRLXgH0KIRQC6RcVXcg letsencrypt.org ; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/85247630
Incident Reporting
Recommendations
  • Consider adding 'issuewild' records to control wildcard certificate issuance