Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=api.mergify.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 19, 2026
Valid Until
July 18, 2026
69 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
94:B4:82:21:C5:32:F6:B3:C5:95:FB:F8:29:98:06:86:C6:2F:8D:38:DB:4B:DC:BF:1D:CD:12:1B:A5:2C:E7:29
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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), attribution-reporting=(); +43 more
Recommendations
- • 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