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

Detected Technologies

See all in URL Inspect 18

Google Trust

Plyr

Calendly

Cookiebot

Google Analytics

Google Cloud Storage

Google Fonts

Google reCAPTCHA

Google Search

Google Static File Front End

Google Tag Manager

G Workspace

Intercom

Storyblok

Stripe

Typeform

Vimeo

Google Cloud

Certificate Information

Subject

CN=gynzy.com

Issuer

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

Valid From

April 24, 2026

Valid Until

July 23, 2026 81 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

30:79:9C:4A:BF:36:66:D7:2A:36:7F:5C:36:4B:57:79:94:17:6A:49:17:A5:76:20:56:45:25:91:40:58:B3:F1

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

Basic

default-src; script-src; style-src; +11 more Analyze

Content-Security-Policy-Report-Only

Missing

Not configured Analyze

X-Frame-Options

Excellent

DENY

X-Content-Type-Options

Good

nosniff

Referrer-Policy

Present

same-origin

Permissions-Policy

Present

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

Recommendations

• Improve CSP by adding more specific directives and removing 'unsafe-inline'

CAA Records (Certificate Authority Authorization)

CAA Records

Configured (Restricts certificate issuance)

Current Issuer

Authorized (Matches CAA policy)

Authorized CAs

quovadisglobal.com pki.goog 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
• Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

2 domains

gynzy.com www.gynzy.com