DNSApe | Fast Network Tools

Settings

Winter snow effect

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.

Maps the domain to IPv4 addresses.

Address	Name	TTL
142.251.46.206	google.com	241s

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).

Maps the domain to IPv6 addresses.

Address	Name	TTL
2607:f8b0:4005:80c:0:0:0:200e	google.com	160s

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.

Authoritative nameservers for this domain.

Nameserver	Name	TTL
ns4.google.com	google.com	343294s
ns2.google.com	google.com	343294s
ns3.google.com	google.com	343294s
ns1.google.com	google.com	343294s

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.

Mail exchange servers with priority (lower = higher priority).

Priority	Mail Server	TTL
10	smtp.google.com	146s

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.

Text records used for verification, SPF, DKIM, and other purposes.

Dgoogle-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ

-docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e

Dgoogle-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0

;facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95

]cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b

+MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB

Dgoogle-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o

#v=spf1 include:_spf.google.com ~all

=onetrust-domain-verification=de01ed21f2fa4d8781cbc3ffb89cf4ef

@globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=

-docusign=1b0a6754-49b1-4db5-8540-d2c12664b289

*apple-domain-verification=30afIBcvSuDV2PLX

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.

Pointer records mapping IP addresses back to hostnames.

Hostname	Name	TTL
nuq04s39-in-f14.1e100.net	238.189.250.142.in-addr.arpa	76071s

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.

Contains administrative information about the DNS zone.

Primary NS: ns1.google.com

Responsible: dns-admin@google@com

Serial

846175965

Refresh

900s

Retry

900s

Expire

1800s

Minimum TTL

60s

Type	Value	Name	TTL
PTR	nuq04s39-in-f14.1e100.net	238.189.250.142.in-addr.arpa	76071
NS	ns4.google.com	google.com	343294
NS	ns2.google.com	google.com	343294
NS	ns3.google.com	google.com	343294
NS	ns1.google.com	google.com	343294
A	142.251.46.206	google.com	241
AAAA	2607:f8b0:4005:80c:0:0:0:200e	google.com	160
MX10	smtp.google.com	google.com	146
TXT	Dgoogle-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ	google.com	3436
TXT	-docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e	google.com	3436
TXT	Dgoogle-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0	google.com	3436
TXT	;facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95	google.com	3436
TXT	]cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b	google.com	3436
TXT	+MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB	google.com	3436
TXT	Dgoogle-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o	google.com	3436
TXT	#v=spf1 include:_spf.google.com ~all	google.com	3436
TXT	=onetrust-domain-verification=de01ed21f2fa4d8781cbc3ffb89cf4ef	google.com	3436
TXT	@globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=	google.com	3436
TXT	-docusign=1b0a6754-49b1-4db5-8540-d2c12664b289	google.com	3436
TXT	*apple-domain-verification=30afIBcvSuDV2PLX	google.com	3436
SOA	Primary NS: ns1.google.com Responsible party: dns-admin@google@com	google.com	22
Serial	Refresh	Retry, Minimum	Expire
846175965	900	900, 60	1800

Your IP: 216.73.216.115

About DNSApe

DNSApe is a fast, no-nonsense network diagnostics toolkit built for developers, sysadmins, and security researchers.

Version History

2.0 - 2025-12-19

Complete rewrite

Rebuilt with Laravel 12, Livewire 3, and Tailwind CSS 4
Live ping monitoring with real-time Chart.js visualization
Email Security tool: SPF, DKIM, DMARC validation
REST API with JSON responses (60 req/min)
MCP server for AI assistant integration (Claude, ChatGPT, etc.)
Slack integration with /dns, /whois, /ssl slash commands
Help tooltips explaining each tool and record type
Shareable ping sessions with unique URLs
Pretty/Raw view toggle with persistent preference
Browser-based ping for client-side latency testing
Enhanced WHOIS with domain + IP info combined
Improved SSL certificate error handling
Full-width responsive layout

Version 2.1 with performance improvements and bug fixes coming soon.

1.1.3 - 2019-04-30

Moved to new infrastructure, resolving most DNS Traversal issues
Replaced RBL with SSL validation tool

1.1.2 - 2019-04-17

Fixed DNS Traversal issue causing many requests to fail

1.1.1 - 2019-04-16

Minor UI adjustments
Added links to lookups in DNS results
Updated dependencies
Increased session timeout to 1 week to eliminate 419 errors
Updated IP address display
Removed dnsape.com as default lookup

1.1 - 2019-02-15

Several UI adjustments
Dark mode setting is persistent between sessions via cookie
Added GDPR cookie banner for session cookies
Added tool to show client IP in lookup field (settings menu)
Keyboard shortcuts for tools, focusing, text size, copying URLs
Shareable lookup URLs - browser address changes with tool usage
Added links to Github repo and feature voting
Several error handling and bug fixes

1.0.7 - 2019-01-11

Fixed HTTP Headers issue with multiple HTTPS redirects

1.0.6 - 2019-01-09

HTTP Headers now forward to and display HTTPS headers
UI adjustments

1.0.5 - 2019-01-08

Dark Mode!

1.0.4 - 2019-01-07

TLD and subdomain validation fixes

1.0.3 - 2019-01-06

Updated DNS Cache host list
IP address validation improvements
Fixed progress bar bug with failed queries
UI adjustments

1.0.2 - 2019-01-05

IPWhois and Ping now work with IP addresses as well as hostnames
Several validation enhancements reduce errors for many lookups
Several UI adjustments

1.0.1 - 2019-01-04

Added Recent Updates panel
Fixed Whois search for many TLDs
Fixed DNS Traversal for many TLDs
Changed to fluid viewport width
Added Privacy Policy

1.0 - 2019-01-02

Initial release