DNS records

twitter.com DNS records

twitter.com 7 record types
RESOLVED
Resolved — 1 IPv4 address returned.
DNS · 11ms · resolver 169.254.100.5
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/twitter.com next.

Records

A
162.159.140.229
AAAAno records
CNAMEno records
MX
1 aspmx.l.google.com5 alt1.aspmx.l.google.com5 alt2.aspmx.l.google.com10 alt3.aspmx.l.google.com10 alt4.aspmx.l.google.com
NS
d.u06.twtrdns.neta.r06.twtrdns.neta.u06.twtrdns.netb.r06.twtrdns.netb.u06.twtrdns.netc.r06.twtrdns.netc.u06.twtrdns.netd.r06.twtrdns.net
TXT
google-site-verification=F2uUiLUsD6kQlpUVQzxUM3PHa0uPo5GBS84SCG8QwXIgoogle-site-verification=P9-NRZ0gaRKRGNDOXOjct5XETPtr3P9D-XA8HnlbAy4google-site-verification=TNhAkfLUeIbzzzSgPNxS5aEkKMf3aUcpPmCK1_kmIvUgoogle-site-verification=h6dJIv0HXjLOkGAotLAWEzvoi9SxqP4vjpx98vrCvvQgoogle-site-verification=q1ghWjGLX9Ba-Gy_B4n_pAgC_mQYzWmQpOD8CMWl_Hwlinear-domain-verification=t5iq7e7nbw5wloom-site-verification=638c6bc173b9458997f64d305bf42499miro-verification=6e1ca9ad6d0c2cd2e4186141265f23ed618cfe37mixpanel-domain-verify=164dda91-31f4-41e8-a816-0f59b38fea30slack-domain-verification=9oO8P4Glf4252QJDOg4rHGs6KlSkBuI5ZVmWRO8dstripe-verification=46F7B88485621DC18923B43D12E90E6CDBCE232F2FEBCF084E6EFA91F6BA707Dtraction-guest=6882b04e-4188-4ff9-8bb4-bff5a3d358e6traction-guest=a4d0248d-fe01-4222-8fcc-33f68323e667v=spf1 ip4:199.16.156.0/22 ip4:199.59.148.0/22 ip4:8.25.194.0/23 ip4:8.25.196.0/23 ip4:204.92.114.203 ip4:204.92.114.204/31 include:_spf.google.com include:_thirdparty.twitter.com -allwrike-verification=MjU4MTA5MjoyN2UzNDc1MjU3MDZiZTY4NjBiNzliNDQ2OTUwNWY3NmM5NDgyMTBlYzFkNTcwYTE2YWNmZDdkNTY2ZmE4Yzlh0a8c0fc6-bfa5-4ea7-b09b-87f2989022d6MS=BEE202D20C326867290BDEFA2DDDF4594B5D6860adobe-idp-site-verification=a2ff8fc40c434d1d6f02f68b0b1a683e400572ab8c1f2c180c71c3d985b9270aapple-domain-verification=zd1iHoEO9LILEQIqatlassian-domain-verification=j6u0o1PTkobCXC84uEF/sWpIPtaZURBVYqKzmTvT8wugLcHT1vvrzzA63iP1qSLNbj6sbt5xqs9hw9jrfvz7hplrg0l680sbcanva-site-verification=lMnZ3wMh7c1uqZqa-cxZTggoogle-site-verification=600dQ0pZYsH2xOFt4hYmf5f5NpjCbWE_qk5Y04dErYM
SOA
nsname a.u06.twtrdns.net
hostmaster noc.twitter.com
serial 2024011501 · refresh 3600s · retry 600s · expire 604800s · minttl 7200s

Operational warnings

What to try next

Compare resolvers

Run dig +short A twitter.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.