DNS records

github.com DNS records

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

Records

A
140.82.114.3
AAAAno records
CNAMEno records
MX
0 github-com.mail.protection.outlook.com
NS
dns1.p08.nsone.netdns2.p08.nsone.netdns3.p08.nsone.netdns4.p08.nsone.netns-1283.awsdns-32.orgns-1707.awsdns-21.co.ukns-421.awsdns-52.comns-520.awsdns-01.net
TXT
loom-site-verification=f3787154f1154b7880e720a511ea664dmiro-verification=d2e174fdb00c71e0bcf58f8e58c3da2dd80dcfa9shopify-verification-code=t1YPwcmvnxZyBycaCpk1MPyWoFs72ostripe-verification=f88ef17321660a01bab1660454192e014defa29ba7b8de9633c69d6b4912217fv=spf1 ip4:192.30.252.0/22 include:spf.protection.outlook.com include:_netblocks.google.com include:_netblocks2.google.com include:mail.zendesk.com include:_spf.salesforce.com include:servers.mcsv.net include:mktomail.com include:sendgrid.net ip4:62.253.227.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~allMS=6BF03E6AF5CB689E315FB6199603BABF2C88D805MS=ms44452932MS=ms58704441TAILSCALE-xOzoDvFUzZr5YYVCQFuDadobe-idp-site-verification=b92c9e999aef825edc36e0a3d847d2dbad5b2fc0e05c79ddd7a16139b48ecf4bapple-domain-verification=RyQhdzTl6Z6x8ZP4atlassian-domain-verification=jjgw98AKv2aeoYFxiL/VFaoyPkn3undEssTRuMg6C/3Fp/iqhkV4HVV7WjYlVeF8calendly-site-verification=at0DQARi7IZvJtXQAWhMqpmIzpvoBNF7aam5VKKxPdocusign=087098e3-3d46-47b7-9b4e-8a23028154cdfacebook-domain-verification=39xu4jzl7roi7x0n93ldkxjiaarx50google-site-verification=82Le34Flgtd15ojYhHlGF_6g72muSjamlMVThBOJpksgoogle-site-verification=UTM-3akMgubp6tQtgEuAkYNYLyYAvpTnnSrDMWoDR3ojamf-site-verification=XtaPNIYghF_e_xRDI8CjgQkrisp-domain-verification=ZlyiK7XLhnaoUQb2hpak1PLY7dFkl1WE
SOA
nsname ns-1707.awsdns-21.co.uk
hostmaster awsdns-hostmaster.amazon.com
serial 1 · refresh 7200s · retry 900s · expire 1209600s · minttl 86400s

Operational warnings

What to try next

Full HTTP probe

Run /check/github.com to see live status, response time, and 24h history.

Compare resolvers

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