DNS Gurus

SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Hostname Mismatch - certificate is issued for *.s3-ap-southeast-1.amazonaws.com, *.s3.amazonaws.com, s3-deprecated.ap-southeast-1.amazonaws.com, *.s3.dualstack.ap-southeast-1.amazonaws.com, *.s3-control.dualstack.ap-southeast-1.amazonaws.com, *.s3-deprecated.ap-southeast-1.amazonaws.com, s3.ap-southeast-1.amazonaws.com, *.s3-accesspoint.ap-southeast-1.amazonaws.com, not for static.dnaindia.com

Cached · just now
75/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
AWS Certificate Manager logo AWS Certificate Manager

Certificate Information

Subject
CN=*.s3-ap-southeast-1.amazonaws.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
November 18, 2025
Valid Until
November 01, 2026 253 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B2:03:A8:4C:C0:84:F7:98:2E:76:5B:2E:DA:61:EE:81:14:BE:97:B6:D6:E3:81:4F:88:56:AA:E5:68:30:06:3D
Alternative Names
16 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
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • 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