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

Detected Technologies

See all in URL Inspect 15

Google Trust

Facebook

Firebase

GitHub

Google Analytics

Google API JS Client

Google Cloud Functions

Google Fonts

Google Search

Google Static File Front End

Google Sign-In

Google Tag Manager

YouTube

Google Cloud

Google Cloud Storage

Certificate Information

Subject

CN=yarlis.com

Issuer

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

Valid From

July 16, 2026

Valid Until

October 14, 2026 61 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

45:89:A9:B3:86:FA:04:2C:32:20:CF:68:A5:7E:A3:0D:A0:90:D8:CE:B3:C3:5F:EA:EA:3A:D5:BB:93:A5:41:B9

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

yarlis.com *.yarlis.com