Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS Certificate Manager
Amazon S3
Bing
Microsoft Advertising
Facebook
Google AdSense
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot CMS
HubSpot Forms
HubSpot Live Chat
Imgix
LinkedIn
Microsoft Clarity
Segment
Sentry
Active incidents
Stripe
Visual Website Optimizer
Zapier
Google Cloud
Certificate Information
Subject
CN=trint.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
December 11, 2025
Valid Until
January 09, 2027
241 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A5:A4:1D:FA:F7:52:E6:41:85:F1:58:1E:12:EE:FB:C4:63:EA:49:DC:0B:29:36:C0:BF:D4:85:77:0D:96:09:DB
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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