Website DNS
Website DNS
Check the DNS record of the website online using this tool
Website DNS
| Type | Host | Class | Target | TTL |
|---|---|---|---|---|
| A | reppaca1.xyz. | IN | 52.222.236.129 | 59 |
| A | reppaca1.xyz. | IN | 52.222.236.103 | 59 |
| A | reppaca1.xyz. | IN | 52.222.236.89 | 59 |
| A | reppaca1.xyz. | IN | 52.222.236.91 | 59 |
| NS | reppaca1.xyz. | IN | ens3.hostcocoa.com. | 86250 |
| NS | reppaca1.xyz. | IN | ens1.hostcocoa.com. | 86250 |
| NS | reppaca1.xyz. | IN | ens4.hostcocoa.com. | 86250 |
| NS | reppaca1.xyz. | IN | ens2.hostcocoa.com. | 86250 |
| TXT | reppaca1.xyz. | IN | "v=spf1 ip4:52.79.92.223 ~all" | 3600 |
Last update on 2024-04-11 20:28:47
렙파카-REPPACA
- Title
- 렙파카-REPPACA
- Description
- 최저가 공장직영 럭셔리사이트,재구매율1위 럭셔리쇼핑몰,매일신상품 업데이트,신규회원가입즉시할인,명품레플리카쇼핑몰,명품레플리카사이트,명품레플사이트,명품레플쇼핑몰,레플샵,명품레플리카가방,명품레플가방,여성레플지갑,남성레플의류,남자레플리카사이트,여성레플리카가방,남자레플리카의류,여성레플리카의류,명품레플지갑,명품레플신발,명품레플시계,미러급핸드폰결제,미러급카드결제,레플리카카드결제
- Link
- reppaca1.xyz
- 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.