Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Gravatar
Let's Encrypt
YouTube
AWS
Amazon S3
Bing
Facebook
Google AdSense
Google Analytics
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
Iconfinder
instant.page
Lead Forensics
LinkedIn
Microsoft Clarity
Recite Me
Termly
Yoast
ZoomInfo
Active incidents
Google Cloud
Certificate Information
Subject
CN=reciteme.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
March 15, 2026
Valid Until
June 13, 2026
40 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
96:B6:B4:D8:8D:79:9C:F6:A5:32:27:DD:AE:FE:4D:CD:F6:38:E4:BA:E0:D5:67:99:F8:F7:5C:AE:E9:9F:DA:40
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
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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