pingy.io
Check a site →

Explore Pingy’s real monitoring data.

Browse the overview and every diagnostic report for pingy.io.

Join beta for free monitoring →

Last collected 50 minutes ago · Sep 15 19:30 UTC

What this means & how to fix it

What the evidence tells you

A certificate proves the server identity and enables encrypted connections. Expiry, hostname mismatch, or an incomplete chain can prevent visitors from connecting.

Suggested next steps

Review the hostname, expiry, and chain in this report. Check certificate renewal at your hosting or CDN provider, install the full chain, and recheck every serving endpoint after changes.

Evidence collected Sep 15, 2026 19:30 UTC. Current settings may have changed since this check.

A+

SSL Certificate Health

Certificate is valid and securely configured.

Last checked 50 minutes ago

Days until expiry
114 days
Jan 7, 2027
Protocol floor
TLS 1.2
Secure
Negotiated
TLS 1.3
Excellent
Chain status
Complete
3 certificates
HSTS
Enabled
Active
Healthy Chain Complete Hostname Match CT Logged HSTS Enabled OCSP Stapled

1. Certificate Overview

Common Name (CN) pingy.io
SAN Subject Alternative Names pingy.io, www.pingy.io
Issuer Amazon
Valid From Jun 24, 2026 00:00 UTC
Expires Jan 7, 2027 23:59 UTC (114 days)
Days Valid (Total) 198 days
Signature Algorithm RSA / SHA256
Key Type / Strength RSA 2048-bit

2. Certificate Chain

3 certs No missing intermediate
🔑
Leaf (Server)
pingy.io
Issuer: Amazon RSA 2048 M01
Expires
114 days
📜
Intermediate
Amazon RSA 2048 M01
Issuer: Amazon Root CA 1
Expires
1438 days
📜
Intermediate
Amazon Root CA 1
Issuer: Starfield Services Root Certificate Authority - G2
Expires
4124 days

3. Security Checks

Expiry
114 days left
Good
Chain Completeness & Order
Complete
Good
Hostname Match
Exact match
Good
Issuer Changes
No change
Good
HSTS
Enabled
Good
Signature Algorithm
RSA / SHA256
Good
Key Strength
RSA 2048-bit
Good
Certificate Transparency
Logged (3 SCTs)
Good
OCSP Stapling
Not stapled
N/A
CAA Alignment
No CAA record
N/A

4. Protocols & Cipher

Current connection
🔒 TLS 1.3
TLS_AES_128_GCM_SHA256
128-bit
Protocol support
SSLv3
Not tested –
TLS 1.0
Not tested –
TLS 1.1
Not tested –
TLS 1.2
Enabled ✓
TLS 1.3
Enabled ✓
Key Exchange
ECDHE
Authentication
RSA
Forward Secrecy
Yes
SCTs (CT)
3

Legacy protocols (SSLv3–TLS 1.1) aren’t actively probed by the scanner. Full cipher & vulnerability scanning is on the roadmap.

5. Security & Policy Details

🛡HSTSStrict-Transport-Security
Present
Max-Age
31,536,000 (365d)
Preload
No
📑Certificate Transparency
Logged
Embedded SCTs · 3
OCSP Stapling / Revocation
Not stapled
Stapled
No
Revocation
Unknown
🔏CAA Alignment
No CAA
CAA records
0 issue tags
Issuer authorized

6. Grade Explanation

Protocol & Cipher20/20
Key Strength20/20
Certificate Chain20/20
HSTS & Security19/20
Expiry & Stability20/20
99 100
  • Trusted certificate, valid hostname, modern TLS.
  • Strong HSTS policy (≥180 days).

7. Recent Certificate Events

This is a certificate snapshot. Pro monitoring tracks renewals, expiry, and trust changes over time.
View full monitor →