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

Detected Technologies

See all in URL Inspect 14

Let's Encrypt

YouTube

Contentsquare

Google Analytics

Google Conversion Tracking

Google DoubleClick

Google Fonts

Google Search

Google Tag Manager

HubSpot

HubSpot Analytics

HubSpot Forms

Netlify

Vector

Certificate Information

Subject

CN=easyclocking.com

Issuer

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

Valid From

March 23, 2026

Valid Until

June 21, 2026 36 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

9E:D7:89:09:D1:27:9B:47:AC:15:F5:0D:32:77:AB:D8:AF:91:38:4C:2E:4C:36:D3:5A:51:C7:7A:6A:92:C1:5D

Alternative Names

1 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; +5 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

Missing

Not configured

Recommendations

• Strengthen CSP by removing 'unsafe-eval'
• Consider adding Permissions-Policy to control browser features

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

1 domain

easyclocking.com