Full HTTP probe
Run /check/discord.com to see live status, response time, and 24h history.
DNS records
discord.com DNS records
discord.com
7 record types
RESOLVED
1s ago
What this means
The hostname resolves and is reachable at the DNS layer. If browsers can't reach it, the issue is downstream of DNS — TLS, HTTP routing, or a firewall block. Try /check/discord.com next.
Records
A
162.159.136.232162.159.138.232162.159.137.232162.159.135.232162.159.128.233
AAAAno records
CNAMEno records
MX
1 aspmx.l.google.com5 alt1.aspmx.l.google.com5 alt2.aspmx.l.google.com10 aspmx3.googlemail.com10 aspmx2.googlemail.com
NS
sima.ns.cloudflare.comgabe.ns.cloudflare.com
TXT
atlassian-domain-verification=JNe2Ze7P8p623k8f7xRaHDyQWb6VzLxjFga1tu8M7lmVXC0bo1XgdnEsYuGIRFHvdocusign=90632817-c176-45ac-9297-96916059c0c5google-site-verification=19lneLj60qA3xv2S96DiWzeNjLZZca3otEPR6KhvrBQgoogle-site-verification=4lTw99D7TJimzNkaj9WtUoOpZoXad73hmD4WgR7COH4google-site-verification=AkZq_nCggw5fS3x2crQxF9I_9MEdqqWIVB-mutOiFzwgoogle-site-verification=P3cQmz_2xQ17u5qOBHf7JIAYGq3HzDq0UtEkbOR6ZjQgoogle-site-verification=Xos4rv9-rY3aGpQ6FtxhUC_Buhef0wF88_4rB4HmTZIgoogle-site-verification=uv4vY9gTOxCxIHlq_V75SMEEvcU44ATbkPcmV0Cpvusslack-domain-verification=hb2Jt7Z5kT0NqJOuGUM2P6L3ZihqWD3wR17JuECtv=spf1 include:_spf.google.com include:mail.zendesk.com include:sendgrid.net include:3885857.spf06.hubspotemail.net ip4:198.2.180.60 -allapple-domain-verification=UP89cBit9taWldL9
SOA
nsname gabe.ns.cloudflare.com
hostmaster dns.cloudflare.com
serial 2401297841 · refresh 10000s · retry 2400s · expire 604800s · minttl 1800s
Operational warnings
- No AAAA records — site is IPv4-only. Modern networks expect both.
What to try next
TLS certificate
Inspect the live cert at /ssl/discord.com.
Compare resolvers
Run dig +short A discord.com @1.1.1.1 and @8.8.8.8 — if they disagree, propagation is still in flight.
Methodology
- Probe
- We resolve A, AAAA, CNAME, MX, NS, TXT, and SOA records in parallel via Node's built-in dns.promises against the system resolver. Every query has a 5-second timeout; non-existent record types are reported as no records rather than errors.
- Counts as DOWN
- All address-resolution attempts fail. The most informative form is NXDOMAIN (the authoritative server explicitly says "no such name"); other forms are server errors or timeouts.
- Counts as DEGRADED
- Reserved for partial responses — some record types resolved, others timed out. Usually a flaky upstream or rate-limited authoritative server.
- Detail
- We surface the records as the resolver returned them, plus operational warnings: missing AAAA (IPv4-only), missing MX (cannot receive mail at the apex), missing SPF in TXT (outbound mail likely flagged as unauthenticated). We do not enumerate zone files, attempt zone transfers (AXFR), or run DNSSEC validation.
- 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.