Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
esm.sh
Gravatar
AWS API Gateway
AWS CloudFront
Google AdSense
Google Maps
Google Tag Manager
Bing
G2
SalesLoft
Maze
Sectigo
AppNexus (Xandr)
Lead Forensics
Liveramp
HubSpot Forms
OptinMonster
Azure Blob Storage
Google DoubleClick
Google Analytics
ClickCease
Microsoft Advertising
Google Conversion Tracking
6sense
Baidu Analytics
Segment
Cloudflare CDN
Google Static File Front End
Outbrain
Google API JS Client
AzureFrontDoor
Google Fonts
Wistia
Twitter
G Workspace
Hotjar
LinkedIn
HubSpot CMS
Zendesk
Azure Monitor
ShareThis
HubSpot Analytics
unpkg
Lottie Player
Google Search
Cloudflare
Active incidents
Demandbase
Facebook
Amazon S3
Buzzsprout
OneTrust
Adobe Fonts (Typekit)
Cloudflare CDNJS
AWS
jQuery
Visual Website Optimizer
Vimeo
IP-API
Google Optimize
Akamai
HubSpot
YouTube
Microsoft Clarity
HubSpot Live Chat
Sentry
jsDelivr
Google Cloud
Microsoft Azure
Google Cloud Storage
Certificate Information
Subject
CN=*.addressy.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
Valid From
December 04, 2025
Valid Until
January 02, 2027
284 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E5:7E:26:E7:C8:30:0B:AF:3B:21:65:D8:D2:A4:38:41:10:D5:F9:4B:27:98:CD:E2:06:AA:F3:B2:9B:DE:70:2A
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=10886400; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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