Open
Cached
·
just now
84/100
SECURITY SCORE
Certificate Information
Subject
CN=maptiler.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 20, 2025
Valid Until
March 20, 2026
56 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
65:72:CD:AC:E3:AB:B5:38:EE:02:E4:6D:CB:87:84:45:3E:A4:2C:0A:11:BC:91:EA:E5:22:77:E1:EB:01:49:1D
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
Missing
Not configured
Content-Security-Policy
Basic
script-src; object-src; base-uri; +1 more
script-src 'report-sample' 'nonce-_2SfkOP4fVWsBpeZgodFEA' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /cspreport
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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