Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
Gravatar
Let's Encrypt
AWS
Buzzsprout
Clickagy
Cloudflare CDNJS
Facebook
Font Awesome
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
jsDelivr
LinkedIn
New Relic
Osano
Segment
YouTube
ZoomInfo
Active incidents
Google Cloud
Certificate Information
Subject
CN=www.coreinfrastructure.org
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
April 13, 2026
Valid Until
July 12, 2026
76 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
76:03:F5:6B:62:C7:25:4D:10:EF:D7:59:33:7F:21:A8:C8:0F:E9:FE:C2:01:D3:D8:C8:AC:EF:44:CA:5F:37:06
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
browsing-topics=(), accelerometer=(), autoplay=(); +20 more
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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