SSL Certificate Analysis for integration.flip.to - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 13

AWS CloudFront

Google Trust

Adobe Fonts (Typekit)

Cloudflare CDNJS

Cloudflare Turnstile

Cloudflare Web Analytics

Google Analytics

Google Fonts

Google Hosted Libraries

Google Tag Manager

Sentry

Webflow

Wistia

Certificate Information

Subject

CN=flip.to

Issuer

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

Valid From

February 17, 2026

Valid Until

May 18, 2026 41 days

Public Key

ECDSA 256 bit (P-256) Adequate

Signature Algorithm

ECDSA-SHA256

SHA-256 Fingerprint

69:AB:95:52:4B:2C:89:06:37:72:35:42:EA:80:00:F5:89:D4:A3:A9:5F:C2:73:E9:B6:A0:27:D3:82:3A:D5:EB

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=31536000; includeSubDomains; preload

Content-Security-Policy

Good

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

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

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

flip.to *.flip.to