Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS CloudFront
Ashby
Google Tag Manager
Bing
Google Hosted Libraries
AppNexus (Xandr)
Liveramp
Google DoubleClick
Google Analytics
Microsoft Advertising
Yoast
6sense
Google Static File Front End
Weglot
Oktopost
Google Fonts
Wistia
Hotjar
LinkedIn
Drift
Google Search
Adobe Marketo
OneTrust
Cloudflare CDNJS
Dun & Bradstreet DirectPlus
jQuery
AWS Certificate Manager
YouTube
Microsoft Clarity
Sentry
jsDelivr
Google Cloud
Certificate Information
Subject
CN=www.semperis.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
August 05, 2025
Valid Until
September 03, 2026
117 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
01:4F:B5:8D:DA:76:9F:9D:12:88:A0:56:2C:D9:74:B1:46:65:F1:A9:57:57:B6:A6:79:11:38:BB:1F:B8:CB:E0
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
Present
strict-origin-when-cross-origin, no-referrer-when-downgrade
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