github.com DNS Records: A, MX, NS and TXT | MemonaIQ

Cached DNS lookup

github.com DNS records

Review the public DNS configuration observed for github.com, including web, mail, nameserver, and security-related records.

A & AAAA
MX & TXT
NS & CNAME

Open DNS Lookup

Lookup observed: 11/8/2026, 11:02:35 AMSource: Public DNS-over-HTTPS resolvers

DNS lookup complete

github.com

Found 41 records across 5 record types.

Response

8152 ms

Records

41

DNS health

47/100

Records at a glance

The DNS services detected for this domain.

A record seen by

Each public resolver was asked separately during this lookup. Answers can differ for a while after a DNS change, until cached copies expire.

CloudflareA record found
GoogleA record found
Quad9No response

What needs attention

Prioritized configuration guidance.

Enable DNSSEC to prevent DNS spoofing and cache poisoning attacks.
Adopt IPv6 by adding AAAA records to future-proof your infrastructure and improve reachability.
Consider adding a secondary MX record for email redundancy.
Found SPF record: v=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.2" "27.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~all

Email provider

Microsoft 365

Address records

A records map github.com to IPv4 destinations, while AAAA records map it to IPv6 destinations. TTL values indicate how long resolvers may cache each answer.

Mail infrastructure

MX records identify receiving mail servers. TXT records commonly carry SPF, DMARC-related policy, and domain-verification values; they should be interpreted in context.

Nameservers and aliases

NS records identify authoritative nameservers. CNAME records alias one hostname to another and cannot normally coexist with other data at the same DNS name.

Freshness and limitations

This is a timestamped, cached observation from public recursive resolvers. DNS answers can vary by location and change before the cache refreshes; it is not an authoritative zone export.

How DNS resolution worksFollow one lookup from your browser through resolvers to the authoritative servers.DNS records for popular domainsSee the cached records for other well-known domains.Open the full DNS LookupLook up any other public domain. No account needed.