Website DNS
Website DNS
Check the DNS record of the website online using this tool
Website DNS
| Type | Host | Class | Target | TTL |
|---|---|---|---|---|
| A | koreatherapy.com. | IN | 198.54.115.239 | 7192 |
| NS | koreatherapy.com. | IN | dns1.namecheaphosting.com. | 86400 |
| NS | koreatherapy.com. | IN | dns2.namecheaphosting.com. | 86400 |
| MX | koreatherapy.com. | IN | 10 mx2-hosting.jellyfish.systems. | 14400 |
| MX | koreatherapy.com. | IN | 5 mx1-hosting.jellyfish.systems. | 14400 |
| MX | koreatherapy.com. | IN | 20 mx3-hosting.jellyfish.systems. | 14400 |
| TXT | koreatherapy.com. | IN | "v=spf1 +a +mx +ip4:198.54.114.111 +ip4:198.54.115.111 include:spf.web-hosting.com ~all" | 14400 |
Last update on 2026-09-21 01:28:37
한국 테라피 TOP 10 — Korea Therapy Rankings 2026
- Title
- 한국 테라피 TOP 10 — Korea Therapy Rankings 2026
- Description
- 2026-2027년 한국 서울 최고의 테라피·마사지·스파 TOP 10. 전문가들이 선정한 프리미엄 스웨디시·로미로미·오일마사지·바디케어 우수 업체를 소개합니다.
- Link
- koreatherapy.com
- Image
-
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.