Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Klaviyo
Adobe Fonts (Typekit)
Calendly
ChatSupport
Cloudflare CDNJS
DigiCert
Facebook
GeoTrust
Google AdSense
Google Analytics
Google Cloud Storage
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
jQuery
jsDelivr
Reddit
Snapchat
TikTok Analytics
The Trade Desk
YouTube
Google Cloud
Microsoft Azure
Certificate Information
Subject
CN=cicispizza.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust TLS RSA CA G1
Valid From
February 19, 2026
Valid Until
August 19, 2026
181 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
52:09:96:0E:D2:4D:EF:75:AF:D0:11:2B:AD:2A:2A:8A:60:0D:2D:79:41:B8:59:22:F0:B5:C9:66:6F:BD:D1:C7
Alternative Names
Security Configuration
TLS Protocols
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=15552000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), autoplay=(); +24 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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