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 secure.paytm.in, accounts.paytm.com, ap.p-y.tm, apiproxy.paytm.com, appcdn.paytm.com, assetscdn.paytm.com, assetscdn1.paytm.com, b.paytm.me, boss-ext.paytm.in, not for staticpg.paytm.in.edgekey.net

Cached · just now
68/100 SECURITY SCORE

Detected Technologies

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

Certificate Information

Subject
C=IN, ST=Uttar Pradesh, L=Noida, O=One 97 Communications Limited, CN=secure.paytm.in
Issuer
C=US, O=DigiCert, Inc., CN=GeoTrust G5 TLS RSA4096 SHA384 2022 CA1
Valid From
February 04, 2026
Valid Until
February 03, 2027 302 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
AC:21:F5:DA:57:F1:7A:D5:39:45:8F:78:69:B8:FA:1A:FB:A2:99:1A:0B:1F:E4:48:34:12:2A:37:43:F5:62:D5
Alternative Names
50 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)
  • • 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
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