SSL Certificate Analysis for www.secureauth.com - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 15

Akamai Active incidents

AWS Certificate Manager

Clickagy

G2

Google Analytics

Google Conversion Tracking

Google DoubleClick

Google Search

Google Tag Manager

Qualified

Sentry

The Trade Desk

Wistia

ZoomInfo

Certificate Information

Subject

CN=secureauth.com

Issuer

C=US, O=Amazon, CN=Amazon RSA 2048 M04

Valid From

March 20, 2026

Valid Until

October 03, 2026 156 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

8F:01:3C:4B:03:9B:55:89:05:E8:71:0C:0D:D5:7C:C3:7E:1D:24:28:84:9F:AC:94:0F:86:3C:60:F7:8A:06:B0

Alternative Names

2 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

Excellent

max-age=63072000; includeSubDomains; preload

Content-Security-Policy

Good

default-src; script-src; style-src; +8 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

Present

camera=(), microphone=(), geolocation=(); +1 more

Recommendations

• Strengthen CSP by removing 'unsafe-eval'

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

secureauth.com www.secureauth.com