Full HTTP probe
Run /check/twitter.com to see live HTTP status, response time, and 24h history alongside this cert.
TLS / SSL certificate
twitter.com TLS certificate
twitter.com
port 443
162.159.140.229
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
- twitter.com
- Issuer
- Let's Encrypt / E7
- Valid from
- Mar 30, 2026, 05:03 AM (26d ago)
- Valid to
- Jun 28, 2026, 05:03 AM (1s ago)
- Days remaining
- 63
- Key
- EC prime256v1
- Signature
- ECDSA-PRIME256V1
- Hostname match
- yes
- SHA-256 fingerprint
- 76:13:68:67:26:4A:97:35:3E:90:58:D6:76:9A:AE:EF:F8:09:5E:E1:65:7C:F9:6C:5F:9A:48:05:1F:32:86:AD
Subject Alternative Names (3)
*.twitter.comcdn.syndication.twitter.comtwitter.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.