DNS lookup: github.com

See every DNS record of a domain in one place, and what they mean: who runs its DNS, where the site and email are hosted, and what's missing.

Try: wikipedia.org · github.com · sitehostingfinder.com

DNS records for github.com

Checked Thu, 12 Nov 2026 14:40:13 UTC via Cloudflare. Results are cached for 2 minutes.

WHAT THESE RECORDS SAY

DNS provider
NS1, Amazon Route 53
Website server
140.82.114.3 · who hosts it?
Email provider
Microsoft 365 · MX details
SPF
present
DMARC
present v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mai full SPF/DKIM/DMARC check
DNSSEC
not signed

A records

NameTypeTTLValue
github.comA24140.82.114.3

AAAA records

No records.

CNAME records

No records.

MX records

NameTypeTTLValue
github.comMX2530 github-com.mail.protection.outlook.com

NS records

NameTypeTTLValue
github.comNS3297dns1.p08.nsone.net
github.comNS3297dns2.p08.nsone.net
github.comNS3297dns3.p08.nsone.net
github.comNS3297dns4.p08.nsone.net
github.comNS3297ns-1283.awsdns-32.org
github.comNS3297ns-1707.awsdns-21.co.uk
github.comNS3297ns-421.awsdns-52.com
github.comNS3297ns-520.awsdns-01.net

TXT records

NameTypeTTLValue
github.comTXT25300Dd0000000hHE0=1TBKg000000TN2r
github.comTXT253MS=6BF03E6AF5CB689E315FB6199603BABF2C88D805
github.comTXT253MS=ms44452932
github.comTXT253MS=ms58704441
github.comTXT253TAILSCALE-xOzoDvFUzZr5YYVCQFuD
github.comTXT253adobe-idp-site-verification=b92c9e999aef825edc36e0a3d847d2dbad5b2fc0e05c79ddd7a16139b48ecf4b
github.comTXT253anthropic-domain-verification-4az7qn=if8YWuRRqwLycGJDooumzHtxm
github.comTXT253apple-domain-verification=RyQhdzTl6Z6x8ZP4
github.comTXT253atlassian-domain-verification=jjgw98AKv2aeoYFxiL/VFaoyPkn3undEssTRuMg6C/3Fp/iqhkV4HVV7WjYlVeF8
github.comTXT253calendly-site-verification=at0DQARi7IZvJtXQAWhMqpmIzpvoBNF7aam5VKKxP
github.comTXT253cursor-domain-verification-gtfwmt=1rfLOtiTngX5QSxD5HvNKTvm3
github.comTXT253docusign=087098e3-3d46-47b7-9b4e-8a23028154cd
github.comTXT253facebook-domain-verification=39xu4jzl7roi7x0n93ldkxjiaarx50
github.comTXT253google-site-verification=82Le34Flgtd15ojYhHlGF_6g72muSjamlMVThBOJpks
github.comTXT253google-site-verification=UTM-3akMgubp6tQtgEuAkYNYLyYAvpTnnSrDMWoDR3o
github.comTXT253jamf-site-verification=XtaPNIYghF_e_xRDI8CjgQ
github.comTXT253krisp-domain-verification=ZlyiK7XLhnaoUQb2hpak1PLY7dFkl1WE
github.comTXT253loom-site-verification=f3787154f1154b7880e720a511ea664d
github.comTXT253miro-verification=d2e174fdb00c71e0bcf58f8e58c3da2dd80dcfa9
github.comTXT253openai-domain-verification=dv-3nh33eQwdkotMIAzLrIDVZo1
github.comTXT253serval-domain-verification-ydryhj=qbkiEakpwEpTvHh5fIiCqtaue
github.comTXT253shopify-verification-code=t1YPwcmvnxZyBycaCpk1MPyWoFs72o
github.comTXT253stripe-verification=f88ef17321660a01bab1660454192e014defa29ba7b8de9633c69d6b4912217f
github.comTXT253v=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 ~all

SOA records

NameTypeTTLValue
github.comSOA900ns-1707.awsdns-21.co.uk awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400

CAA records

NameTypeTTLValue
github.comCAA36000 issue "digicert.com"
github.comCAA36000 issue "globalsign.com"
github.comCAA36000 issue "letsencrypt.org"
github.comCAA36000 issue "sectigo.com"
github.comCAA36000 issuewild "digicert.com"
github.comCAA36000 issuewild "letsencrypt.org"
github.comCAA36000 issuewild "sectigo.com"

DMARC (_dmarc.github.com)

NameTypeTTLValue
_dmarc.github.comTXT208v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1

www.github.com

NameTypeTTLValue
www.github.comCNAME3600github.com

What each DNS record does

RecordWhat it's for
AThe IPv4 address of the server that hosts the site. Changing hosts means changing this.
AAAAThe IPv6 address of the server, if it has one.
CNAMEAn alias: "www.example.com is the same as example.myhost.com". Common for www and for platforms like Shopify.
MXMail servers that receive email for the domain, in priority order (lowest number first).
NSName servers: the company that answers DNS for the domain. Records must be edited there.
TXTFree-text records: SPF, ownership checks for Google or other services, DKIM keys.
CAAWhich certificate authorities may issue SSL certificates for the domain.
SOAStart of authority: the primary name server, admin contact and timing values for the zone.

How this lookup works

We ask public DNS resolvers (Cloudflare first, Google as a fallback) over encrypted DNS-over-HTTPS, the same answer your visitors' browsers get. TTL is how many seconds resolvers may cache a record before asking again, which is why DNS changes can take time to show everywhere. If you just changed a record, use the propagation checker to compare several resolvers at once.

The summary at the top is our reading of the records: the DNS provider comes from the name servers, the email provider from the MX records, and the warnings flag common mistakes such as two SPF records or a missing DMARC policy.

FAQ

How do I look up the DNS records of a domain?

Type the domain into the box above and choose "ALL" to see every record type at once, or pick one type. On a computer you can also run nslookup -type=any example.com or dig example.com ANY, but many servers no longer answer ANY queries, which is why this tool asks for each type separately.

Why do I see different results from my own computer?

Your computer and router cache DNS answers for the TTL period, and your internet provider's resolver has its own cache. After a change, old answers can linger for minutes to hours. Flushing your local DNS cache or waiting out the TTL fixes it.

What is a TTL and what should it be?

TTL (time to live) is how long, in seconds, resolvers may cache a record. 3600 (one hour) is a common default. Before moving hosts, lower it to 300 a day ahead so the switch spreads quickly, then raise it again afterwards.

Is this the same as nslookup?

It does the same job as nslookup and dig, from a browser: no command line needed, and it shows every record type plus an explanation of what the records mean.

Do you store the domains I look up?

Results are cached in memory for two minutes to reduce load, then discarded. Lookup pages are not indexed by search engines.

CHANGING HOSTS?

DNS is where most migrations go wrong. Follow the hosting switch checklist, lower your TTL a day before, and use the propagation checker after the switch. Comparing new hosts? See real renewal prices.

More free tools