DNS Gurus
Cached · just now
84/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 15
Google Trust logo Google Trust Google Analytics logo Google Analytics Google API JS Client logo Google API JS Client Google Cloud Functions logo Google Cloud Functions Google Cloud Run logo Google Cloud Run Google Conversion Tracking logo Google Conversion Tracking Google DoubleClick logo Google DoubleClick Google Optimize logo Google Optimize Google Search logo Google Search Google Static File Front End logo Google Static File Front End Google Tag Manager logo Google Tag Manager YouTube logo YouTube Google App Engine logo Google App Engine Google Cloud logo Google Cloud Google Cloud Storage logo Google Cloud Storage

Certificate Information

Subject
CN=*.google.com
Issuer
C=US, O=Google Trust Services, CN=WR2
Valid From
August 10, 2026
Valid Until
November 02, 2026 65 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8F:95:CC:30:E8:8F:6B:71:EF:35:1F:71:03:32:85:0C:55:44:E7:59:4A:F4:0B:1A:7E:11:9E:18:EF:D6:10:22
Alternative Names
65 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
Missing
Not configured
Content-Security-Policy
Google Conversion Tracking logo
Basic
script-src; object-src; img-src; +3 more Analyze
Content-Security-Policy-Report-Only
Weak
require-trusted-types-for; report-uri Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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