Web Tools
DNS Record Validator
Check DNS record values before adding them to a provider.
DNS record
Validation result
No blocking errors@ MX 10 mail.example.com 3600s TTLThe record shape looks ready to paste into a DNS provider. This does not confirm that the record is published on the internet.
Normalized fields
About This Tool
DNS setup often fails because of small copy-and-paste mistakes: a full URL where a hostname is expected, an invalid IP address, a missing MX priority, an SPF value without v=spf1, or a CAA value in the wrong shape. This validator checks the structure of common DNS records locally before you paste them into Cloudflare, a registrar, email provider, or hosting dashboard. It does not perform a live DNS lookup; it helps catch format mistakes before publication.
How To Use It
- Choose the DNS record type you are preparing.
- Enter the name or host, record value, optional TTL, and MX priority when needed.
- Review errors and warnings. Errors indicate a record shape that should be fixed before saving.
- Copy the readable summary if you need to document or compare the record. Confirm final requirements with your DNS provider because provider-specific rules can vary.
Examples
Website A record
An A record with name @ and value 192.0.2.10 passes when the value is a valid IPv4 address.
Email MX record
An MX record needs both a mail hostname such as mail.example.com and a numeric priority such as 10.
SPF TXT record
An SPF value should start with v=spf1 and usually end with an all mechanism such as -all or ~all.
Useful Notes
What this checks
The validator checks common structural rules for A, AAAA, CNAME, MX, TXT, SPF, NS, and CAA records. It catches malformed IP addresses, hostname values that accidentally include protocols or paths, missing MX priority, invalid TTL shape, long TXT warnings, SPF prefix issues, and basic CAA syntax.
What this does not check
This tool does not query DNS, inspect propagation, verify nameservers, check whether a record already exists, or confirm that a provider will accept every edge case. Use your DNS dashboard and live DNS lookup tools after saving records.
Root and subdomain names
Many DNS dashboards use @ for the root domain and labels such as www, api, or _dmarc for subdomains. Some providers automatically append the zone domain, so paste only the host part when that is what the dashboard asks for.
TTL and future changes
TTL controls how long resolvers may cache a DNS answer. Very long TTLs can make future changes slower to appear, while very short TTLs may not be allowed on every provider. This tool flags unusually low or very long values.
Privacy and safety
Validation runs locally in the browser and does not send record values anywhere. Avoid pasting secret verification tokens into public messages or screenshots even though DNS TXT records may become publicly visible after publication.
FAQ
Does this check DNS propagation?
No. It validates record format locally before saving. Propagation requires live DNS queries after the record is published.
Why is a full URL invalid for CNAME, MX, or NS?
Those record values expect hostnames such as target.example.com, not URLs with https://, paths, query strings, or fragments.
Can I use it for Cloudflare records?
Yes, it is useful before adding records in Cloudflare, but Cloudflare-specific features such as proxy status, flattened CNAME behavior, or zone-level restrictions still need to be reviewed in Cloudflare.
Is SPF a separate DNS record type?
Modern SPF is normally published as a TXT record. This tool includes an SPF option as a focused TXT-value checker because SPF mistakes are common during email setup.
Related Tools
URL Parser & Inspector
Inspect URL components and query parameters.
HTTP Status Code Lookup
Find HTTP status meanings and next steps.
Meta Tag Previewer
Preview search and social snippets from page metadata.
Robots.txt Tester
Check robots.txt rules for a crawler and path.