DNS Gurus
Cached · just now
90/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 2
DigiCert logo DigiCert GeoTrust logo GeoTrust

Certificate Information

Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 78, 90>>}, UNKNOWN={:asn1_OPENTYPE, <<12, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN=3069886, C=NZ, L=Auckland, O=Secured Signing Limited, CN=securedsigning.com
Issuer
C=US, O=DigiCert Inc, CN=GeoTrust EV RSA CA G2
Valid From
April 21, 2026
Valid Until
November 05, 2026 189 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
E8:DA:92:C3:9D:90:AF:A6:52:2B:2C:D7:9B:3B:73:90:47:B1:61:AC:0B:87:61:F0:13:67:92:BD:C5:96:FF:03
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=31536000; includeSubDomains; preload, max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Present
nosniff, nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
geolocation=(), midi=(), sync-xhr=(); +5 more
Recommendations
  • • Add Content-Security-Policy header to prevent XSS attacks

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