DNS Gurus
Cached · just now
88/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 8
Let's Encrypt logo Let's Encrypt Facebook logo Facebook Google Analytics logo Google Analytics Google Conversion Tracking logo Google Conversion Tracking Google DoubleClick logo Google DoubleClick Google Search logo Google Search Google Tag Manager logo Google Tag Manager Microsoft Clarity logo Microsoft Clarity

Certificate Information

Subject
CN=uengage.in
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
July 30, 2026
Valid Until
October 28, 2026 88 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F1:DE:46:D4:40:A0:9E:5F:EB:06:F9:52:31:19:ED:18:8E:D9:6D:F2:46:17:23:69:28:CA:2A:95:9C:2F:FF:19
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
Missing
Not configured
Content-Security-Policy
Google Conversion Tracking logo
Basic
default-src; script-src; style-src; +5 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
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'
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Wildcard CAs
letsencrypt.org
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts

Subject Alternative Names

2 domains
uengage.in www.uengage.in