DNS Gurus
Cached · just now
93/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 5
Let's Encrypt logo Let's Encrypt Google reCAPTCHA logo Google reCAPTCHA Google Search logo Google Search Google Static File Front End logo Google Static File Front End Google Cloud logo Google Cloud

Certificate Information

Subject
CN=api.magnetdadi.com
Issuer
C=US, O=Let's Encrypt, CN=YE2
Valid From
September 06, 2026
Valid Until
December 05, 2026 89 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
C1:25:EC:E7:2D:2C:23:31:4E:9F:AA:12:42:37:83:8E:58:59:9A:A8:3E:F0:5C:95:77:AA:7E:9D:24:AD:9A:BD
Alternative Names
6 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
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Google reCAPTCHA logo
Basic
default-src; script-src; style-src; +7 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=()
Recommendations
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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