SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for c.openstreetmap.org, c.osm.org, communities.openstreetmap.org, communities.osm.org, community.openstreetmap.org, community.osm.org, forum.openstreetmap.org, forum.osm.org, not for community.openstreetmap.com
Open
Cached
·
2h ago
89/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=community.openstreetmap.org
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
February 24, 2026
Valid Until
May 25, 2026
45 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
21:6B:38:89:2F:AE:A8:74:E7:56:36:BC:8F:8F:D8:F0:5E:A8:F8:90:A0:90:A5:5B:5A:5E:D7:97:05:69:8B:54
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