Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=simpletexting.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 12, 2025
Valid Until
March 12, 2026
59 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
1A:F2:A1:30:BF:37:E6:F8:41:06:36:3A:C1:6A:DE:1E:FE:73:9D:EA:97:29:7A:C4:D8:AD:57:68:80:67:7C:A9
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
Content-Security-Policy
Basic
base-uri; default-src; frame-ancestors; +2 more
base-uri 'self';default-src 'unsafe-eval' 'unsafe-inline' * blob: data: wss:;frame-ancestors 'self' *.simpletexting.com;object-src 'none';report-uri https://o465048.ingest.sentry.io/api/5480429/security/?sentry_key=c299d519732540b98b96eb7fc256b4ec&sentry_environment=content&sentry_release=2025-12-29T07:52:27+00:00;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
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'
- • Add X-Content-Type-Options: nosniff
- • 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