Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS CloudFront
Google AdSense
Google Tag Manager
Bing
Google Hosted Libraries
Outgrow
HubSpot Forms
Cookiebot
Google DoubleClick
Google Analytics
ClickCease
Microsoft Advertising
Google Conversion Tracking
Cloudflare CDN
Leadfeeder
Google Fonts
LinkedIn
HubSpot CMS
HubSpot Analytics
Google Search
Cloudflare
Active incidents
Facebook
Amazon S3
Cloudflare CDNJS
AWS
AWS Certificate Manager
HubSpot
Intercom
Quora
YouTube
Microsoft Clarity
Sentry
jsDelivr
Certificate Information
Subject
CN=*.regulaforensics.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
June 04, 2026
Valid Until
December 18, 2026
144 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
78:CB:C4:96:E6:D0:BF:72:69:4F:9E:3D:65:65:DF:1B:72:41:F0:58:14:6D:F5:0D:D6:38:48:CE:C7:EF:BF:BF
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
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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