Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Google Trust
Plyr
AWS CloudFront
Google Tag Manager
Bing
Spotify
Google Hosted Libraries
Webflow
HubSpot Forms
Google DoubleClick
Google Analytics
Cloudflare CDN
Greenhouse
Google Static File Front End
Ghost
Google Fonts
Twitter
Cloudflare Web Analytics
Hotjar
LinkedIn
HubSpot Analytics
Google Search
Cloudflare
Active incidents
Facebook
Amazon S3
CookieYes
Vimeo
ipify
HubSpot
YouTube
Microsoft Clarity
HubSpot Live Chat
Sentry
jsDelivr
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=easyship.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 23, 2026
Valid Until
July 22, 2026
84 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F6:09:67:49:27:86:00:A9:37:2E:08:05:A7:3E:4E:DA:F8:B5:C4:F7:45:0B:74:58:9F:8E:24:BA:6A:26:70:8D
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=15552000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(), camera=(); +16 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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