Full HTTP probe
Run /check/discord.com to see live HTTP status, response time, and 24h history alongside this cert.
TLS / SSL certificate
discord.com TLS certificate
discord.com
port 443
162.159.137.232
VALID
1s ago
What this means
Browsers will accept this certificate. Plan a renewal before the expiry date below — most CAs auto-renew at 30 days remaining.
Certificate details
- Subject CN
- discord.com
- Issuer
- Google Trust Services / WE1
- Valid from
- Mar 4, 2026, 02:11 PM (51d ago)
- Valid to
- Jun 2, 2026, 03:11 PM (1s ago)
- Days remaining
- 38
- Key
- EC prime256v1
- Signature
- ECDSA-PRIME256V1
- Hostname match
- yes
- SHA-256 fingerprint
- E3:39:A6:84:3B:0F:48:90:E9:BC:50:CA:6C:88:2A:31:8D:D2:38:CB:C6:43:B6:C8:B7:11:C4:F4:76:DD:2D:0C
Subject Alternative Names (2)
discord.com*.discord.com
What to try next
Renewal reminder
Set a 30-day-before-expiry calendar reminder. Most outages caused by expired certs come from missed renewals.
Check related
Compare with related services or apex/subdomain combinations to spot inconsistencies.
Methodology
- Probe
- We open a TLS handshake to port 443 with the supplied hostname as the SNI, read the peer certificate via getPeerCertificate(true), and validate the hostname against subjectAlternativeName via tls.checkServerIdentity.
- Counts as DOWN
- The TLS handshake fails entirely (TCP refused, handshake timeout, or rejected ClientHello) — we couldn't read a certificate at all.
- Counts as DEGRADED
- Reserved for soon-to-expire certificates and warning-only validation issues like a self-signed cert. Browsers may still warn even when our check labels the cert valid.
- Detail
- All certificate details come from getPeerCertificate(true) on the established socket. We do not enumerate cipher suites, test downgrade attacks, or scan for protocol-level weaknesses; this is read-only certificate inspection.
- Cadence
- Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
- Rate-limited targets
- If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
- Data source
- Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.