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

Detected Technologies

See all in URL Inspect 8

Google Trust

Firebase

Google API JS Client

Google Cloud Functions

Google Fonts

Google Static File Front End

Stripe

Google Cloud

Certificate Information

Subject

CN=autographmd.com

Issuer

C=US, O=Google Trust Services, CN=WR3

Valid From

July 22, 2026

Valid Until

October 20, 2026 80 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

8B:6D:B8:49:C9:DF:14:D7:6A:C4:96:03:AC:8E:7C:AA:EC:3F:A9:39:F0:0B:C1:B8:92:BE:7C:DB:D8:7F:94:6E

Alternative Names

4 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; +6 more Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Good

SAMEORIGIN

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Good

strict-origin-when-cross-origin

Permissions-Policy

Present

camera=(), microphone=(), geolocation=()

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

4 domains

autographscribe.com www.autographscribe.com

Other domains in certificate

autographmd.com www.autographmd.com