Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
YouTube
Acquia Optimize
Ahrefs
AWS
Azure Blob Storage
Facebook
Freshworks
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
HubSpot
HubSpot Analytics
HubSpot Forms
Issuu
Leadfeeder
LinkedIn
OneTrust
Sanity
Vercel
Vimeo
Google Cloud
Certificate Information
Subject
CN=azets.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
March 25, 2026
Valid Until
June 23, 2026
44 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D2:B9:79:4B:42:38:E8:70:09:26:4F:CE:37:B1:F5:7D:A5:D8:44:5D:EB:19:B0:B7:2A:0C:4E:95:B2:91:5B:16
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
Present
max-age=63072000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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