Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Akamai
AWS
Amazon S3
Captivate
Contentful
DigiCert
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
Plaid
Sentry
6sense
Stripe
Termly
Wistia
YouTube
Google Cloud
Certificate Information
Subject
C=US, ST=Utah, L=Lehi, O=Simpler Postage, Inc., CN=*.easypost.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1
Valid From
June 11, 2025
Valid Until
July 12, 2026
66 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
7A:F9:43:71:EA:8A:74:FB:FD:8C:6F:CC:C6:CF:45:D7:30:BC:1D:0F:63:98:DD:19:0A:AE:85:E2:1B:2B:9B:11
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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