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 01032005.link, www.01032005.link, not for ec2-3-108-154-143.ap-south-1.compute.amazonaws.com

Cached · just now
85/100 SECURITY SCORE

Certificate Information

Subject
CN=01032005.link
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 06, 2025
Valid Until
February 04, 2026 45 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3D:57:A0:AA:EE:86:18:2B:6E:BA:45:A5:66:4D:39:B5:EC:EC:7C:97:AB:68:8D:74:6F:19:46:CE:05:2F:58:53
Alternative Names
2 domains

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31536000;
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Present
SAMEORIGIN *.digitaldukaan.app *.dotpe.in
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(self)
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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

Subject Alternative Names

2 domains
01032005.link
www.01032005.link