Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=fonts.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 11, 2026
Valid Until
April 11, 2026
86 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
3B:A9:05:8E:91:B6:05:B5:AD:B7:DC:3D:F1:C5:E3:E6:24:72:73:7F:2F:4D:EF:28:C5:A1:EC:8F:7A:73:B7:FD
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Good
frame-ancestors; media-src; connect-src; +10 more
frame-ancestors 'self';media-src 'self' js.intercomcdn.com; connect-src 'self' https://cdn.cookielaw.org api-iam.intercom.io nexus-websocket-a.intercom.io api-iam.intercom.io nexus-websocket-a.intercom.io wss://nexus-websocket-a.intercom.io cdn.cookielaw.org geolocation.onetrust.com www.google-analytics.com *.clarity.ms stats.g.doubleclick.net;default-src 'self';frame-src 'self' intercom-sheets.com; script-src 'self' *.intercomcdn.com *.heapanalytics.com www.googletagmanager.com cdn.cookielaw.org platform.twitter.com www.clarity.ms www.google-analytics.com static.ads-twitter.com widget.intercom.io 'unsafe-inline';style-src 'self' 'unsafe-inline' www.googletagmanager.com fonts.googleapis.com;font-src 'self' fonts.googleapis.com fonts.gstatic.com fonts.intercomcdn.com;img-src 'self' *.intercomcdn.com fonts.gstatic.com fast.fonts.net heapanalytics.com cdn.cookielaw.org c.clarity.ms t.co analytics.twitter.com c.bing.com www.google.com www.google.com.np https://www.googletagmanager.com static.intercomassets.com data:;object-src 'none';base-uri 'self';form-action 'self';upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports