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:

Invalid Certificate - the server's certificate is malformed or invalid

Cached · just now
88/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 35
AWS CloudFront logo AWS CloudFront Google Tag Manager logo Google Tag Manager Bing logo Bing Google reCAPTCHA logo Google reCAPTCHA Fullstory logo Fullstory Reddit logo Reddit HubSpot Forms logo HubSpot Forms HubSpot Feedback & Surveys logo HubSpot Feedback & Surveys Google DoubleClick logo Google DoubleClick Google Analytics logo Google Analytics Google Conversion Tracking logo Google Conversion Tracking Segment logo Segment New Relic logo New Relic Google Static File Front End logo Google Static File Front End Google API JS Client logo Google API JS Client TikTok Analytics logo TikTok Analytics Google Fonts logo Google Fonts Clickagy logo Clickagy Wistia logo Wistia Algolia logo Algolia LinkedIn logo LinkedIn Zendesk logo Zendesk Contentful logo Contentful ZoomInfo logo ZoomInfo Active incidents HubSpot Analytics logo HubSpot Analytics Google Search logo Google Search Facebook logo Facebook Pinterest logo Pinterest HubSpot logo HubSpot YouTube logo YouTube The Trade Desk logo The Trade Desk Microsoft Clarity logo Microsoft Clarity Sentry logo Sentry jsDelivr logo jsDelivr Google Cloud logo Google Cloud

Certificate Information

Subject
O=Acme Co, CN=Kubernetes Ingress Controller Fake Certificate
Issuer
O=Acme Co, CN=Kubernetes Ingress Controller Fake Certificate
Valid From
April 12, 2026
Valid Until
April 12, 2027 364 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A9:75:F5:C1:1C:65:C5:48:E2:57:D3:60:04:69:7D:65:54:2F:DC:7F:30:D9:02:2B:21:16:09:98:71:69:6F:F9
Alternative Names
1 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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
AWS CloudFront logo
Basic
default-src; script-src; style-src; +5 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • 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
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

1 domain
ingress.local