Look up a domain's DNS records in real time.
NetCheck queries Google's public DNS resolver live (over DNS-over-HTTPS) and shows the answer as is. Each record type has a precise role:
| Type | Role | Example value |
|---|---|---|
| A | Maps the name to an IPv4 address | 203.0.113.10 |
| AAAA | Maps the name to an IPv6 address | 2001:db8::10 |
| CNAME | Makes a name an alias of another name | www to example.com |
| MX | Names the servers that receive email, with a priority | 10 mx1.example.com |
| TXT | Free text: ownership proofs, SPF, DKIM, DMARC | v=spf1 include:_spf.google.com ~all |
| NS | The name servers authoritative for the domain | ns1.provider.net |
| SOA | The zone's authority record: primary server, serial number, cache timers | - |
| CAA | The authorities allowed to issue certificates for the domain | 0 issue "letsencrypt.org" |
Every DNS answer carries a TTL (time to live), in seconds. It is how long resolvers around the world may keep the answer in memory without asking again. A TTL of 3600 means a change may take up to an hour to be seen everywhere. Before a migration, lower the TTL to 300 (five minutes) the day before, make the change, then raise it again once everything is checked. To follow a change in progress, use the DNS Propagation tool.
Most emails that land in spam can be explained by TXT records.
v=spf1. Two separate SPF records invalidate both: merge them.selector._domainkey.example.com, which your email provider gives you._dmarc.example.com, says what to do with messages that fail these checks: let them through (p=none), send them to spam (p=quarantine) or reject them (p=reject). Gmail and Yahoo now require it from bulk senders.To read a DKIM or DMARC record, type the relevant subdomain directly, for example _dmarc.example.com, and choose the TXT type.
example.com), because it would clash with the NS and SOA records. Some DNS providers offer “CNAME flattening” or an ALIAS type to work around the rule.“No records” does not necessarily mean something is wrong: many domains have no AAAA or CAA, and that is normal. However, a domain with neither A nor AAAA cannot serve a website, and a domain without MX cannot receive email. If the resolver says the domain does not exist (code 3, known as NXDOMAIN), check the spelling, then its status with the WHOIS tool.
This tool is a DNS lookup in your browser: enter a domain, pick a record type, and NetCheck queries Google's public resolver. If you prefer the command line, these commands return the same records from your own machine:
| Record type | nslookup (Windows, macOS, Linux) | dig (macOS, Linux) |
|---|---|---|
| A | nslookup -type=A example.com | dig example.com A +short |
| AAAA | nslookup -type=AAAA example.com | dig example.com AAAA +short |
| MX | nslookup -type=MX example.com | dig example.com MX +short |
| TXT | nslookup -type=TXT example.com | dig example.com TXT +short |
| NS | nslookup -type=NS example.com | dig example.com NS +short |
| CNAME | nslookup -type=CNAME www.example.com | dig www.example.com CNAME +short |
To ask the same resolver as NetCheck, add its address: nslookup -type=MX example.com 8.8.8.8 or dig @8.8.8.8 example.com MX. In Windows PowerShell, Resolve-DnsName example.com -Type MX gives the same result.
ipconfig /flushdns clears the local cache.dig @ns1.provider.net example.com A skips every cache and shows what the zone actually contains. It is the fastest way to confirm a fresh change before every resolver has picked it up.Yes: the query goes live to Google's public resolver, over DNS-over-HTTPS. But that resolver, like all others, honours the TTL: right after a change it may still return the old value. The DNS Propagation tool compares several resolvers at once.
An A record gives an IP address directly. A CNAME points to another name, which is then resolved in turn. It is handy when the destination address changes often (platforms, CDNs), but it adds a step and cannot coexist with other records on the same name.
It is the priority: the lower it is, the higher the server's priority. Senders try the server with the smallest value first, then move on to the next ones if it does not answer.
It restricts which certificate authorities may issue a certificate for your domain. Without CAA, any of them can; with it, an unlisted authority must refuse, which reduces the risk of a fraudulent certificate.
Both send DNS queries. nslookup comes preinstalled on Windows and gives a short output. dig is standard on Linux and macOS and shows more detail, such as the TTL of each answer and which server replied.
The answer came from a resolver, not directly from the domain's own name server. That is the normal case, not an error. You get an authoritative answer by querying one of the domain's name servers directly.
Usually your provider's resolver or your computer still holds an older answer in cache. It disappears once the TTL has expired at the latest. On Windows, ipconfig /flushdns clears the local cache straight away.
Check whether your DNS is up to date around the world.
OpenA domain's owner, creation date and expiry date.
OpenA site's HTTPS validity, issuer and expiry date.
OpenA URL's server, redirects, caching and security headers.
OpenYour public IP, your provider, your approximate location.
Open