DNS Gurus
Cached · just now
90/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 4
Google Static File Front End logo Google Static File Front End jsDelivr logo jsDelivr Sectigo logo Sectigo Google Cloud logo Google Cloud

Certificate Information

Subject
CN=*.numiga.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
Valid From
July 01, 2025
Valid Until
July 01, 2026 52 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
73:B9:0B:41:EF:A1:4E:BF:6C:6D:EA:94:5C:2C:F5:7B:FA:2C:31:B3:56:D9:94:CF:67:8B:4D:6A:48:FF:3E:A0
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
Content-Security-Policy
jsDelivr logo
Basic
default-src; img-src; media-src; +10 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-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

2 domains
numiga.com *.numiga.com