DNS Records
Complete DNS record set for this domain — A, AAAA, CNAME, MX, NS, TXT, SPF, SRV, PTR, and SOA records.
A Records (IPv4)
A Records (IPv4)
An A (Address) record maps a domain name to an IPv4 address, allowing browsers and other clients to locate the server hosting a website or service. This is the most fundamental DNS record type for connecting human-readable domain names to machine-readable IP addresses.
Common Uses
- Pointing a domain (example.com) to a web server's IPv4 address
- Creating subdomains that resolve to specific servers (blog.example.com, mail.example.com)
- Load balancing by returning multiple A records for the same domain (round-robin DNS)
Valid Settings
Any valid IPv4 address in dotted-decimal notation (e.g., 192.0.2.1). Values must be in the range 0.0.0.0 to 255.255.255.255. Multiple A records can exist for the same hostname.
History
A records were defined in RFC 1035 in 1987 as part of the original DNS specification by Paul Mockapetris. They remain the primary method for IPv4 address resolution and are the most commonly queried DNS record type.
A Records (IPv4)
An A (Address) record maps a domain name to an IPv4 address, allowing browsers and other clients to locate the server hosting a website or service. This is the most fundamental DNS record type for connecting human-readable domain names to machine-readable IP addresses.
Common Uses
- Pointing a domain (example.com) to a web server's IPv4 address
- Creating subdomains that resolve to specific servers (blog.example.com, mail.example.com)
- Load balancing by returning multiple A records for the same domain (round-robin DNS)
Valid Settings
Any valid IPv4 address in dotted-decimal notation (e.g., 192.0.2.1). Values must be in the range 0.0.0.0 to 255.255.255.255. Multiple A records can exist for the same hostname.
History
A records were defined in RFC 1035 in 1987 as part of the original DNS specification by Paul Mockapetris. They remain the primary method for IPv4 address resolution and are the most commonly queried DNS record type.
Maps the domain to IPv4 addresses.
| Address | Name | TTL |
|---|---|---|
| 140.82.112.4 | github.com | 0s |
AAAA Records (IPv6)
AAAA Records (IPv6)
An AAAA (quad-A) record maps a domain name to an IPv6 address, serving the same purpose as A records but for the newer 128-bit IPv6 addressing system. As IPv4 addresses become exhausted, AAAA records are increasingly important for modern internet infrastructure.
Common Uses
- Enabling IPv6 connectivity for websites and services
- Dual-stack configuration where both A and AAAA records exist for the same domain
- Future-proofing infrastructure as the internet transitions from IPv4 to IPv6
Valid Settings
Any valid IPv6 address in colon-hexadecimal notation (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334 or shortened as 2001:db8:85a3::8a2e:370:7334). Addresses are 128 bits represented as eight groups of four hexadecimal digits.
History
AAAA records were defined in RFC 3596 in 2003 to support IPv6 addressing. The name 'AAAA' was chosen because IPv6 addresses are four times larger than IPv4 addresses (128 bits vs 32 bits).
AAAA Records (IPv6)
An AAAA (quad-A) record maps a domain name to an IPv6 address, serving the same purpose as A records but for the newer 128-bit IPv6 addressing system. As IPv4 addresses become exhausted, AAAA records are increasingly important for modern internet infrastructure.
Common Uses
- Enabling IPv6 connectivity for websites and services
- Dual-stack configuration where both A and AAAA records exist for the same domain
- Future-proofing infrastructure as the internet transitions from IPv4 to IPv6
Valid Settings
Any valid IPv6 address in colon-hexadecimal notation (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334 or shortened as 2001:db8:85a3::8a2e:370:7334). Addresses are 128 bits represented as eight groups of four hexadecimal digits.
History
AAAA records were defined in RFC 3596 in 2003 to support IPv6 addressing. The name 'AAAA' was chosen because IPv6 addresses are four times larger than IPv4 addresses (128 bits vs 32 bits).
Maps the domain to IPv6 addresses.
| Address | Name | TTL |
|---|---|---|
| 64:ff9b::8c52:7003 | github.com | 0s |
NS Records (Nameservers)
NS Records (Nameservers)
An NS (Name Server) record delegates a DNS zone to a specific authoritative name server, indicating which servers are responsible for answering DNS queries for that domain. NS records form the foundation of DNS's hierarchical structure.
Common Uses
- Delegating subdomains to different name servers
- Specifying which name servers are authoritative for a domain
- Creating redundancy by listing multiple authoritative name servers for a zone
Valid Settings
A fully qualified domain name (FQDN) of a name server. Multiple NS records should exist for redundancy (typically 2-4). NS records appear both at the zone apex and in the parent zone to create proper delegation.
History
NS records were defined in RFC 1035 in 1987 as a core component of the DNS specification. They enable the distributed, hierarchical nature of DNS by allowing different organizations to manage different parts of the domain name space.
NS Records (Nameservers)
An NS (Name Server) record delegates a DNS zone to a specific authoritative name server, indicating which servers are responsible for answering DNS queries for that domain. NS records form the foundation of DNS's hierarchical structure.
Common Uses
- Delegating subdomains to different name servers
- Specifying which name servers are authoritative for a domain
- Creating redundancy by listing multiple authoritative name servers for a zone
Valid Settings
A fully qualified domain name (FQDN) of a name server. Multiple NS records should exist for redundancy (typically 2-4). NS records appear both at the zone apex and in the parent zone to create proper delegation.
History
NS records were defined in RFC 1035 in 1987 as a core component of the DNS specification. They enable the distributed, hierarchical nature of DNS by allowing different organizations to manage different parts of the domain name space.
Authoritative nameservers for this domain.
| Nameserver | Name | TTL |
|---|---|---|
| ns-1707.awsdns-21.co.uk | github.com | 0s |
| ns-421.awsdns-52.com | github.com | 0s |
| ns-520.awsdns-01.net | github.com | 0s |
| dns1.p08.nsone.net | github.com | 0s |
| dns2.p08.nsone.net | github.com | 0s |
| dns3.p08.nsone.net | github.com | 0s |
| dns4.p08.nsone.net | github.com | 0s |
| ns-1283.awsdns-32.org | github.com | 0s |
MX Records (Mail Servers)
MX Records (Mail Servers)
An MX (Mail Exchange) record specifies which mail servers are responsible for accepting email on behalf of a domain, along with a priority value that determines the order in which servers should be tried.
Common Uses
- Directing email to mail servers (mail sent to [email protected] goes to mail.example.com)
- Setting up backup mail servers with different priority values for redundancy
- Routing email to third-party email providers (Google Workspace, Microsoft 365)
Valid Settings
A priority value (0-65535, lower numbers indicate higher priority) followed by a fully qualified domain name of a mail server. Multiple MX records with different priorities provide failover capability.
History
MX records were defined in RFC 974 in 1986 and later refined in RFC 1035. They were created to separate mail routing from the host's A record, allowing organizations to use dedicated mail servers.
MX Records (Mail Servers)
An MX (Mail Exchange) record specifies which mail servers are responsible for accepting email on behalf of a domain, along with a priority value that determines the order in which servers should be tried.
Common Uses
- Directing email to mail servers (mail sent to [email protected] goes to mail.example.com)
- Setting up backup mail servers with different priority values for redundancy
- Routing email to third-party email providers (Google Workspace, Microsoft 365)
Valid Settings
A priority value (0-65535, lower numbers indicate higher priority) followed by a fully qualified domain name of a mail server. Multiple MX records with different priorities provide failover capability.
History
MX records were defined in RFC 974 in 1986 and later refined in RFC 1035. They were created to separate mail routing from the host's A record, allowing organizations to use dedicated mail servers.
Mail exchange servers with priority (lower = higher priority).
Detected Email Service
| Priority | Mail Server | TTL |
|---|---|---|
| 0 | github-com.mail.protection.outlook.com Microsoft 365 | 0s |
TXT Records
TXT Records
A TXT (Text) record stores arbitrary text data associated with a domain, originally intended for human-readable notes but now primarily used for machine-readable configuration and verification data.
Common Uses
- Domain ownership verification for third-party services (Google, Microsoft, SSL CAs)
- Email authentication protocols (SPF, DKIM, DMARC policies)
- Storing configuration data for various services and security mechanisms
Valid Settings
Any text string up to 255 characters per segment. Content is enclosed in double quotes. Common formats include key=value pairs and structured policies like SPF.
History
TXT records were defined in RFC 1035 in 1987 to allow arbitrary text annotations. While originally intended for human-readable comments, they've evolved to become critical infrastructure for email security (SPF in 2006) and domain validation.
TXT Records
A TXT (Text) record stores arbitrary text data associated with a domain, originally intended for human-readable notes but now primarily used for machine-readable configuration and verification data.
Common Uses
- Domain ownership verification for third-party services (Google, Microsoft, SSL CAs)
- Email authentication protocols (SPF, DKIM, DMARC policies)
- Storing configuration data for various services and security mechanisms
Valid Settings
Any text string up to 255 characters per segment. Content is enclosed in double quotes. Common formats include key=value pairs and structured policies like SPF.
History
TXT records were defined in RFC 1035 in 1987 to allow arbitrary text annotations. While originally intended for human-readable comments, they've evolved to become critical infrastructure for email security (SPF in 2006) and domain validation.
Text records used for verification, SPF, DKIM, and other purposes.
PTR Records (Reverse DNS)
PTR Records (Reverse DNS)
A PTR (Pointer) record performs reverse DNS lookup by mapping an IP address back to a hostname, essentially the opposite of A and AAAA records. PTR records are stored in special reverse lookup zones.
Common Uses
- Email server verification (many mail servers reject email from IPs without valid PTR records)
- Network troubleshooting and logging (converting IP addresses to readable hostnames)
- Security and abuse investigations (identifying the organization behind an IP address)
Valid Settings
A fully qualified domain name (FQDN) that the IP address resolves to. PTR records are stored in reverse zones: IPv4 uses '.in-addr.arpa' (e.g., 1.2.0.192.in-addr.arpa for 192.0.2.1).
History
PTR records were defined in RFC 1035 in 1987 as part of the original DNS specification. Reverse DNS became increasingly important in the 1990s for email verification and spam prevention.
PTR Records (Reverse DNS)
A PTR (Pointer) record performs reverse DNS lookup by mapping an IP address back to a hostname, essentially the opposite of A and AAAA records. PTR records are stored in special reverse lookup zones.
Common Uses
- Email server verification (many mail servers reject email from IPs without valid PTR records)
- Network troubleshooting and logging (converting IP addresses to readable hostnames)
- Security and abuse investigations (identifying the organization behind an IP address)
Valid Settings
A fully qualified domain name (FQDN) that the IP address resolves to. PTR records are stored in reverse zones: IPv4 uses '.in-addr.arpa' (e.g., 1.2.0.192.in-addr.arpa for 192.0.2.1).
History
PTR records were defined in RFC 1035 in 1987 as part of the original DNS specification. Reverse DNS became increasingly important in the 1990s for email verification and spam prevention.
Pointer records mapping IP addresses back to hostnames.
| Hostname | Name | TTL |
|---|---|---|
| lb-140-82-114-3-iad.github.com | 3.114.82.140.in-addr.arpa | 5s |
SOA Record (Start of Authority)
SOA Record (Start of Authority)
An SOA (Start of Authority) record marks the beginning of a DNS zone and contains critical metadata about the zone, including the primary name server, contact email, serial number, and timing parameters. Every DNS zone must have exactly one SOA record.
Common Uses
- Defining authoritative information about a DNS zone and its administrator
- Controlling zone transfer behavior between primary and secondary name servers
- Managing DNS caching behavior and update propagation timing
Valid Settings
Contains seven fields: primary name server (MNAME), responsible email (RNAME, @ replaced by .), serial number (typically YYYYMMDDNN), refresh interval, retry interval, expire time, and minimum TTL. Example refresh: 3600-86400 seconds.
History
SOA records were defined in RFC 1035 in 1987 as part of the original DNS specification. They were designed to support DNS's distributed architecture with zone replication and cache management.
SOA Record (Start of Authority)
An SOA (Start of Authority) record marks the beginning of a DNS zone and contains critical metadata about the zone, including the primary name server, contact email, serial number, and timing parameters. Every DNS zone must have exactly one SOA record.
Common Uses
- Defining authoritative information about a DNS zone and its administrator
- Controlling zone transfer behavior between primary and secondary name servers
- Managing DNS caching behavior and update propagation timing
Valid Settings
Contains seven fields: primary name server (MNAME), responsible email (RNAME, @ replaced by .), serial number (typically YYYYMMDDNN), refresh interval, retry interval, expire time, and minimum TTL. Example refresh: 3600-86400 seconds.
History
SOA records were defined in RFC 1035 in 1987 as part of the original DNS specification. They were designed to support DNS's distributed architecture with zone replication and cache management.
Contains administrative information about the DNS zone.
| Type | Value | Name | TTL |
|---|---|---|---|
| PTR | lb-140-82-114-3-iad.github.com | 3.114.82.140.in-addr.arpa | 5 |
| NS | ns-1707.awsdns-21.co.uk | github.com | 0 |
| NS | ns-421.awsdns-52.com | github.com | 0 |
| NS | ns-520.awsdns-01.net | github.com | 0 |
| NS | dns1.p08.nsone.net | github.com | 0 |
| NS | dns2.p08.nsone.net | github.com | 0 |
| NS | dns3.p08.nsone.net | github.com | 0 |
| NS | dns4.p08.nsone.net | github.com | 0 |
| NS | ns-1283.awsdns-32.org | github.com | 0 |
| A | 140.82.112.4 | github.com | 0 |
| AAAA | 64:ff9b::8c52:7003 | github.com | 0 |
| MX0 | github-com.mail.protection.outlook.com | github.com | 0 |
| TXT | MS=ms58704441 | github.com | 0 |
| TXT | TAILSCALE-xOzoDvFUzZr5YYVCQFuD | github.com | 0 |
| TXT | adobe-idp-site-verification=b92c9e999aef825edc36e0a3d847d2dbad5b2fc0e05c79ddd7a16139b48ecf4b | github.com | 0 |
| TXT | anthropic-domain-verification-4az7qn=if8YWuRRqwLycGJDooumzHtxm | github.com | 0 |
| TXT | apple-domain-verification=RyQhdzTl6Z6x8ZP4 | github.com | 0 |
| TXT | atlassian-domain-verification=jjgw98AKv2aeoYFxiL/VFaoyPkn3undEssTRuMg6C/3Fp/iqhkV4HVV7WjYlVeF8 | github.com | 0 |
| TXT | calendly-site-verification=at0DQARi7IZvJtXQAWhMqpmIzpvoBNF7aam5VKKxP | github.com | 0 |
| TXT | docusign=087098e3-3d46-47b7-9b4e-8a23028154cd | github.com | 0 |
| TXT | facebook-domain-verification=39xu4jzl7roi7x0n93ldkxjiaarx50 | github.com | 0 |
| TXT | google-site-verification=82Le34Flgtd15ojYhHlGF_6g72muSjamlMVThBOJpks | github.com | 0 |
| TXT | google-site-verification=UTM-3akMgubp6tQtgEuAkYNYLyYAvpTnnSrDMWoDR3o | github.com | 0 |
| TXT | jamf-site-verification=XtaPNIYghF_e_xRDI8CjgQ | github.com | 0 |
| TXT | krisp-domain-verification=ZlyiK7XLhnaoUQb2hpak1PLY7dFkl1WE | github.com | 0 |
| TXT | loom-site-verification=f3787154f1154b7880e720a511ea664d | github.com | 0 |
| TXT | miro-verification=d2e174fdb00c71e0bcf58f8e58c3da2dd80dcfa9 | github.com | 0 |
| TXT | shopify-verification-code=t1YPwcmvnxZyBycaCpk1MPyWoFs72o | github.com | 0 |
| TXT | stripe-verification=f88ef17321660a01bab1660454192e014defa29ba7b8de9633c69d6b4912217f | github.com | 0 |
| TXT | 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.227.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~all | github.com | 0 |
| TXT | 00Dd0000000hHE0=1TBKg000000TN2r | github.com | 0 |
| TXT | MS=6BF03E6AF5CB689E315FB6199603BABF2C88D805 | github.com | 0 |
| TXT | MS=ms44452932 | github.com | 0 |
| SOA |
Primary NS: ns-1707.awsdns-21.co.uk
Responsible party: [email protected]
|
github.com | 0 |
| Serial | Refresh | Retry, Minimum | Expire |
| 1 | 7200 | 900, 86400 | 1209600 |