DNS Gurus
Cached · just now
88/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Google Trust logo Google Trust

Certificate Information

Subject
CN=stackdriver.com
Issuer
C=US, O=Google Trust Services, CN=WR2
Valid From
April 20, 2026
Valid Until
July 13, 2026 54 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3F:93:83:B4:3D:F1:87:1B:AB:F2:A5:AC:5C:5E:11:96:6E:60:C4:A9:16:FF:9B:E3:51:04:E3:75:3F:BD:38:59
Alternative Names
4 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Basic
script-src; object-src; base-uri; +3 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*; +6 more
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)

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