Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=verticurl.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 01, 2026
Valid Until
April 01, 2026
69 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
30:86:14:E8:5B:2D:24:76:F6:D9:90:3C:35:2F:2F:B4:5E:05:5C:EF:F7:4A:E8:C7:1D:81:3E:2A:88:51:4E:4B
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=63072000;
Content-Security-Policy
Basic
script-src; script-src-elem; default-src; +3 more
script-src 'self' 'unsafe-eval' www.google.com *.google.com *.googletagmanager.com tagmanager.google.com cdn.jsdelivr.net *.google-analytics.com *.cloudflare.com googletagmanager.com *.gstatic.com; script-src-elem 'self' 'unsafe-inline' www.google.com *.googletagmanager.com googletagmanager.com tagmanager.google.com www.googletagmanager.com cdn.jsdelivr.net cdn-cookieyes.com cookieyes.com log.cookieyes.com *.google.com *.cloudflare.com *.google-analytics.com *.gstatic.com; default-src 'self' 'unsafe-inline' www.google.com *.googletagmanager.com googletagmanager.com tagmanager.google.com www.googletagmanager.com cdn.jsdelivr.net cdn-cookieyes.com cookieyes.com log.cookieyes.com *.googleapis.com *.gstatic.com *.cloudflare.com *.google-analytics.com www.google.com *.google.com; img-src 'self' *.google.com www.google.com *.cloudflare.com *.gstatic.com data: *; object-src 'none' *.cloudflare.com *.gstatic.com *.google.com; *.cloudflare.com
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
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