Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
C=AE, L=Dubai, O=Media.Net Advertising FZ-LLC, CN=*.media.net
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
August 24, 2025
Valid Until
August 25, 2026
289 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5F:1F:28:AF:AC:B6:4D:EC:56:C9:E0:4A:35:09:89:C1:15:EE:E2:FA:47:7A:79:BA:F7:B4:EF:09:F8:27:A7:C5
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=2628000
Content-Security-Policy
Good
default-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(*), autoplay=(self), camera=(self), encrypted-media=(self), fullscreen=(*), geolocation=(self), gyroscope=(self), magnetometer=(), midi=(), payment=(), picture-in-picture=(*), sync-xhr=(*), usb=(self )
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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