Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
Cloudflare CDNJS
Facebook
G2
Google AdSense
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
Active incidents
HubSpot Analytics
Active incidents
HubSpot Forms
Active incidents
Intellimize (Webflow)
jsDelivr
LinkedIn
OneTrust
Qualified
Sentry
6sense
unpkg
Webflow
Wistia
Google Cloud
Certificate Information
Subject
CN=reputation.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 19, 2026
Valid Until
July 18, 2026
79 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
70:C4:EF:53:67:A7:4A:B5:B1:2E:04:13:8C:36:D8:33:92:30:78:B4:9E:44:2F:C1:DD:21:71:DA:62:D4:CE:FB
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
Good
max-age=31536000; includeSubDomains
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
- • Consider adding 'preload' to HSTS for maximum security
- • 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