DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 2
Let's Encrypt logo Let's Encrypt Google Analytics logo Google Analytics

Certificate Information

Subject
CN=forum.webpushr.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
April 17, 2026
Valid Until
July 16, 2026 72 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
B2:E6:B2:89:A9:A3:4F:DD:6C:BA:90:FD:DE:2D:A3:91:76:3D:E5:4D:80:4F:52:3B:45:3A:00:9F:E3:7B:24:30
Alternative Names
1 domains

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
Google Analytics logo
Basic
upgrade-insecure-requests; base-uri; object-src; +4 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
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

Subject Alternative Names

1 domain
forum.webpushr.com