AK
appkiro.comLook up A, AAAA, MX, NS, CNAME, TXT, and SOA records for a public domain.
DNS Lookup is useful when you need to see what a domain is publishing right now, without opening a terminal or switching between several provider dashboards. Enter the domain, choose the record type, and the result shows the raw answer returned by DNS resolution.
Different DNS records answer different problems. If a website is not loading, check A or AAAA. If email is not arriving, MX is usually the first stop. For ownership checks, email policies, and provider verification, TXT is often where the clue lives.
The output is intentionally plain. DNS data is easier to troubleshoot when it is not over-processed. If a record is missing, the domain may not publish that record type, the change may still be propagating, or the value may be managed by a different DNS provider than expected.
When you have just changed DNS, check the same record again later instead of assuming the first answer is final. Resolver caches and TTLs can make old values appear for a while.
CLI equivalent
dig example.com ANetwork checks run from the app server, so results reflect what is reachable from that public environment. Localhost, private IPs, and internal-only targets are blocked.
No. Use the domain name only, such as example.com. The tool is checking DNS records, not loading a web page.
Not every domain has every record type. For example, a root domain may have A records but no CNAME, while a verification subdomain may only have TXT.
Yes. DNS can be affected by resolver cache, TTL, recent changes, and provider routing. If the value was just changed, compare again after the TTL window.