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

Detected Technologies

See all in URL Inspect 13

Let's Encrypt

Firebase

Fontshare

Google AdSense

Google Analytics

Google API JS Client

Google Conversion Tracking

Google DoubleClick

Google Fonts

Google Static File Front End

Google Tag Manager

jsDelivr

Google Cloud

Certificate Information

Subject

CN=py-loft.com

Issuer

C=US, O=Let's Encrypt, CN=YE1

Valid From

June 24, 2026

Valid Until

September 22, 2026 39 days

Public Key

ECDSA 256 bit (P-256) Adequate

Signature Algorithm

ECDSA-SHA384

SHA-256 Fingerprint

61:F7:F8:60:21:23:13:68:7F:40:FB:EC:50:54:73:2E:29:37:A4:A1:C9:35:FB:DD:16:8F:8E:AF:16:EF:B7:FB

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

Basic

default-src; script-src; frame-src; +9 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=()

Recommendations

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

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

py-loft.com www.py-loft.com