SSL Certificate Analysis for www.refiner.io - Security Grade & TLS Configuration

Detected Technologies

See all in URL Inspect 12

AWS Certificate Manager

Fathom Analytics

Google Analytics

Google Conversion Tracking

Google DoubleClick

Google Fonts

Google Search

Google Tag Manager

HubSpot

HubSpot Forms

jsDelivr

Certificate Information

Subject

CN=www.refiner.io

Issuer

C=US, O=Amazon, CN=Amazon RSA 2048 M02

Valid From

August 09, 2025

Valid Until

September 05, 2026 160 days

Public Key

RSA 2048 bit Adequate

Signature Algorithm

SHA256-RSA

SHA-256 Fingerprint

7E:1E:19:C3:02:49:8D:D2:68:BF:D8:D3:C3:DD:DA:E9:C3:EB:B5:46:EA:71:4B:FF:E0:A4:61:14:32:F0:9C:72

Alternative Names

1 domains

Security Configuration

TLS Protocols

TLS 1.1 TLS 1.2 TLS 1.3

Forward Secrecy

Supported (Modern clients use PFS)

Warnings

• TLS 1.1 is deprecated and should be disabled

HTTP Security Headers

Status

Strict-Transport-Security

Present

max-age=63072000; includeSubdomains; preload

Content-Security-Policy

Basic

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

Present

same-origin

Permissions-Policy

Present

geolocation=(self)

Recommendations

• Increase HSTS max-age to at least 1 year and add includeSubDomains
• 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

1 domain

www.refiner.io