Website DNS

Website DNS

Check the DNS record of the website online using this tool

Website DNS

Type Host Class Target TTL
A radutny.com. IN 198.12.237.162 7135
NS radutny.com. IN ns17.domaincontrol.com. 3600
NS radutny.com. IN ns18.domaincontrol.com. 3600
MX radutny.com. IN 20 mx2-us1.ppe-hosted.com. 3600
MX radutny.com. IN 10 mx1-us1.ppe-hosted.com. 3600
TXT radutny.com. IN "v=spf1 a:dispatch-us.ppe-hosted.com include:secureserver.net -all" 3600
TXT radutny.com. IN "google-site-verification=ALFz6TjgEz5IVU6zvC4rmZ-ecxGLo7rUPvA2rdY56FM" 3600
TXT radutny.com. IN "MS=ms50662350" 3600

Last update on 2025-11-11 06:57:36

Vladimir Radutny Architects

Vladimir Radutny Architects

Title
Vladimir Radutny Architects
Description
Born in Chicago on August 16th, 2008, our multi-disciplinary Architecture practice focuses on innovative design solutions that challenge the conventional interpretations of space, function, and material use.
Image
Vladimir Radutny Architects

Enter a domain and this tool queries its DNS records directly: A/AAAA for IP addresses, MX for mail routing, TXT for verification and SPF/DKIM records, NS for nameservers, and more. It's built for confirming a DNS change has actually propagated, or figuring out why email or a site isn't resolving the way it should.

Enter a domain like this to see its live DNS records:

example.com → A, MX, NS, TXT and other records currently published for that domain

Why don't I see my recent DNS change yet?

DNS changes take time to propagate because of caching (TTL) at resolvers around the world. A change can take anywhere from a few minutes to about 48 hours to show up everywhere.

What does an MX record tell me?

It tells you which mail servers are responsible for receiving email for that domain, in priority order.

Why would a domain have multiple TXT records?

TXT records get used for several unrelated things at once: domain verification, SPF for email senders, DKIM keys, and more. So a domain often ends up with several.

Does this tool query my own DNS cache?

No, it queries DNS records directly, so it reflects what is actually published, independent of any caching on your own device or network.