netpulse.fyi
LIVE
🌐 Network
πŸ“‘Ping ToolπŸ”ŒPort CheckerπŸ”„Reverse DNSπŸ—ΊοΈIP LookupπŸ”Site Status
πŸ” DNS
πŸ”ŽDNS Lookup🌍DNS PropagationπŸ“§MX Records
πŸ“§ Email Auth
πŸ›‘οΈSPF CheckerπŸ”‘DKIM CheckerπŸ“‹DMARC Checker
πŸ”’ Security
πŸ”SSL CertificateπŸ“„HTTP HeadersπŸ“WHOIS Lookup
πŸ”Ž

DNS Lookup

Query DNS resolvers to find the IP addresses and records associated with any domain. Queries both Cloudflare and Google in parallel.

Domain

How DNS works

DNS (Domain Name System) translates human-readable domain names into IP addresses. When you type a URL, your device asks a DNS resolver for the IP address. The resolver either answers from cache or queries a chain of authoritative servers: root DNS servers, TLD servers, then the domain's nameservers.

DNS record types

A records map domains to IPv4 addresses. AAAA records map to IPv6. CNAME records alias one domain to another. MX records define mail servers. TXT records store SPF, DKIM, DMARC and verification data. NS records specify authoritative nameservers. SOA records contain zone administration information.

Why use multiple resolvers?

Querying both Cloudflare and Google simultaneously helps diagnose propagation issues and identify resolver-specific caching problems. If one resolver shows outdated results while another shows new values, propagation is still in progress.

TTL and caching

Every DNS record has a TTL value in seconds that tells resolvers how long to cache it. TTL 3600 means cache for 1 hour. Lower TTLs mean faster propagation but higher query volume to your nameservers. Before DNS changes, temporarily lower TTL to 300 seconds (5 minutes) to speed the transition.