Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=docs.arryved.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 26, 2025
Valid Until
February 24, 2026
49 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
BB:F0:D0:DA:BB:06:AF:0A:A8:A6:19:FC:3B:65:EA:0B:20:4C:4F:49:7C:D7:39:AA:7C:81:4F:29:E2:1A:C3:9D
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
Content-Security-Policy
Basic
base-uri; object-src; script-src; +1 more
base-uri 'self'; object-src 'none'; script-src 'nonce-0VYreJrVwdNvXEam5XBcc5NLtM4RyGNwhldmN6IQbFs3roLS0NSI3nXJSzL9j39p' 'strict-dynamic'; report-uri https://o59832.ingest.sentry.io/api/1197065/security/?sentry_key=be62e2ea3fb544f78dd5fbf3abbd8b8a;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • 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