Open
Cached
·
3h ago
91/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Google Tag Manager
Bing
Google reCAPTCHA
Fullstory
Reddit
HubSpot Forms
HubSpot Feedback & Surveys
Google DoubleClick
Google Analytics
Google Conversion Tracking
Segment
New Relic
Google Static File Front End
Google API JS Client
TikTok Analytics
Google Fonts
Clickagy
Wistia
Algolia
LinkedIn
Zendesk
Contentful
ZoomInfo
HubSpot Analytics
Google Search
Facebook
Pinterest
HubSpot
YouTube
The Trade Desk
Microsoft Clarity
Sentry
jsDelivr
Google Cloud
Certificate Information
Subject
CN=test.myobdev.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 05, 2026
Valid Until
June 03, 2026
51 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
29:C9:F9:82:36:FC:EC:E3:CF:59:08:2D:AA:CA:99:A8:AA:AF:D7:C5:94:78:99:24:23:10:33:40:14:96:A2:E7
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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