DNS Gurus
Cached · just now
91/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 7
GitHub logo GitHub Let's Encrypt logo Let's Encrypt Amazon S3 logo Amazon S3 Azure Blob Storage logo Azure Blob Storage GitHub Copilot logo GitHub Copilot Google Cloud Storage logo Google Cloud Storage Microsoft Azure logo Microsoft Azure

Certificate Information

Subject
CN=opensource.puresol-technologies.com
Issuer
C=US, O=Let's Encrypt, CN=YE2
Valid From
August 18, 2026
Valid Until
November 16, 2026 40 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
40:2C:AD:A5:49:20:20:3C:B1:40:08:7A:15:B5:6D:41:6B:1F:07:60:04:AA:A4:4B:E2:E4:46:6D:7C:1F:73:2C
Alternative Names
2 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; includeSubdomains; preload
Content-Security-Policy
GitHub logo
Good
default-src; base-uri; child-src; +12 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin, strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Strengthen CSP by removing 'unsafe-eval'
  • • 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