Use This Tool To Lookup, And Validate Your DNS Records.
Google's Gmail sender guidelines require SPF or DKIM for all senders, and SPF, DKIM and DMARC for senders of 5,000 or more messages per day to personal Gmail accounts. Google recommends configuring all three to strengthen email authentication. Google sender guidelines
Microsoft recommends using SPF, DKIM and DMARC together to strengthen email authentication and protection against spoofing. DMARC helps receiving mail systems evaluate messages that fail domain-aligned authentication, according to the published policy. Microsoft Learn guidance
An A record maps a DNS hostname to one IPv4 address. A host may have several A records for load distribution, and each answer is an IPv4 address, not an alias.
A records let browsers and other network clients find an IPv4 destination for websites, APIs and other hostname-based services.
An A record does not identify an email sender or enforce email authentication. An MX hostname may resolve using A and/or AAAA records.
A addresses are used for IPv4 routing. They do not prove mail delivery, DKIM signing or DMARC enforcement.
Use the tool above to check a hostname. For a manual check, query the same DNS name and record type with dig or nslookup.
Run the free lookup above or enter the query in a terminal.
$ dig A example.com +shortValidate that the returned IPv4 address belongs to the intended provider. For multiple answers, confirm each address is authorized and reachable.
$ nslookup -type=A example.comUse your DNS host or service provider’s published values as the source of truth. Changes can take time to propagate through DNS caches.
example.comexample.com. 3600 IN A 203.0.113.10Illustrative documentation-only IPv4 address. Replace it with a provider-assigned address before publishing.
Interpret the response carefully:
| Result | What it means and what to do |
|---|---|
| No answer returned | No A record may be normal for IPv6-only hosts, aliases or names not intended to resolve. Check whether the service actually requires IPv4. |
| Unexpected or conflicting value | An unexpected address can misroute web traffic or signal a stale configuration; DNS data alone does not prove compromise. |
| Verify published configuration | Compare the host and IPv4 address against your provider configuration. Update records carefully and allow for DNS cache TTLs. |
Enter the hostname in the lookup tool, or run dig A example.com +short in a terminal. Query the specific host used by your DNS or service provider.
No A record may be normal for IPv6-only hosts, aliases or names not intended to resolve. Check whether the service actually requires IPv4.
Compare the host and IPv4 address against your provider configuration. Update records carefully and allow for DNS cache TTLs.
A addresses are used for IPv4 routing. They do not prove mail delivery, DKIM signing or DMARC enforcement.