Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Google Trust
Microsoft Advertising
Cloudflare CDNJS
Cloudflare Turnstile
Cloudflare Web Analytics
Cloudflare Workers
Entri
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Search
Google Tag Manager
HubSpot
HubSpot Analytics
Active incidents
HubSpot Feedback & Surveys
HubSpot Forms
HubSpot Live Chat
Iubenda
LinkedIn
Mixpanel
Paddle
Reddit
Sentry
Active incidents
Stripe
Vimeo
Certificate Information
Subject
CN=pubhtml.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 01, 2026
Valid Until
June 30, 2026
49 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
74:05:F9:40:31:6D:C6:77:36:C4:23:1A:CB:62:AE:2C:37:37:77:4B:74:02:DE:AC:59:E0:34:0C:57:42:A7:07
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(self), geolocation=()
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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