Infrastructure / BROWSER-ONLY UTILITY
Supplied DNS Record Reviewer
Review the record rows you have, with their source and observation time. A partial extract cannot establish what an authoritative zone currently contains.
Add a name, type and value for each record. TTL, source and observation time are optional. Enter TXT policy text without surrounding quotes. Limit: 100,000 characters.
Loading local tool code...
Input stays in this tab. No upload, AI call, analytics or ads. Reset clears the workspace. Clipboard copies and downloaded files remain under your control.
Result
Technical details (optional)
Review the result before sharing. It may still contain personal or confidential information.
Copy the record details, not a whole zone file
Add one record per row using its full name, type and value. A name such as www.example.test is clearer than an abbreviated zone-relative label. Underscores are accepted for service and policy names. TTL is optional and uses whole seconds. Source and observation time help explain where the extract came from; leave them blank when unknown.
Supported value checks
A, AAAA, CNAME, NS, MX and CAA values receive selected syntax checks. MX uses priority followed by exchange, such as 10 mail.example.test.; the 0 . null-MX form is supported. CAA uses flags, tag and a quoted value. TXT is supplied as one unquoted string. Other record types are retained with an explicit unchecked-syntax note, not treated as invalid by absence of support.
Conflicts and policy hints
The reviewer identifies supplied owners that combine CNAME with ordinary records, distinct CNAME targets and multiple distinct SPF strings. An unrestricted SPF all mechanism receives a review point. A DMARC p=none policy is described as monitoring, not automatically insecure. Duplicate rows remain visible because they may be repeated observations or mixed captures rather than distinct authoritative records.
No network conclusions
No resolver is contacted. DNSSEC, propagation, authority, delegation, SPF include expansion, mail alignment and complete-zone coverage are not established. Missing records in your extract do not prove that a domain lacks them. Keep observation context with any exported rows and validate intended changes through your normal DNS change process.
References
- DNS record structures, RFC 1035
- Sender Policy Framework, RFC 7208
- DMARC policy, RFC 9989
- Null MX, RFC 7505
Documentation reviewed: . Rule results describe the supplied text, not a live application test.
Useful next steps
Maintained by MetaCyberGuru. A review point may need source, runtime or deployment context before you act on it.