Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Adobe Audience Manager
Adobe Fonts (Typekit)
Akamai
Akamai mPulse
Microsoft Advertising
Demandbase
DigiCert
GitHub
Active incidents
Google Analytics
Google API JS Client
Google DoubleClick
Google Hosted Libraries
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
Kaltura
LinkedIn
Liveramp
Optimizely
PubMatic
Reddit
Segment
Sonobi
Tapad
Tealium
The Trade Desk
TrustArc
Twitter
YouTube
Google Cloud
Certificate Information
Subject
C=US, ST=New York, L=Armonk, O=International Business Machines Corporation, CN=*.cloudant.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
September 30, 2025
Valid Until
September 29, 2026
40 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
71:8E:8D:AF:A8:51:D2:A9:07:C6:73:49:07:89:FF:9F:CE:9C:7F:6C:37:B5:25:B2:4E:1F:3C:01:8F:44:DE:CE
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=31536000
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
- • 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