botchains.com - dns.ninja

botchains.com

DNSSEC⚠️ Not signed
A52.20.84.62πŸ‡ΊπŸ‡Έ Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-20-84-62.compute-1.amazonaws.com
NSns1.atom.com ⭐
A44.219.81.145πŸ‡ΊπŸ‡Έ Amazon44.192.0.0/11 EC2 IAD prefix
PTRec2-44-219-81-145.compute-1.amazonaws.com
NSns2.atom.com
A50.19.240.86πŸ‡ΊπŸ‡Έ Amazon50.19.128.0/17 EC2 IAD prefix
PTRec2-50-19-240-86.compute-1.amazonaws.com
TXTf0095018235b8109a2bf9f65674a1784b6971ed6
SOAns1.atom.comhostmaster@botchains.com 2024-03-05 #1

com

Same first word

Similar names

DNS History

8 records (3 active, 5 former)

201820192020202120222023202420252026NSns1.atom.comns2.atom.comdns103.ovh.netns103.ovh.netMXredirect.ovh.netA52.20.84.62164.132.235.172001:41d0:301::23
β—‹NSdns103.ovh.net2017-08-11 β†’ 2017-08-11 Β· 3 obs
● 2017-08-11 06:18:04
β—‹ 2026-02-18 13:25:28
β—‹ 2026-06-21 05:51:38
●NSns1.atom.com2026-02-18 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-08-11 06:18:04
● 2026-02-18 13:25:28
● 2026-06-21 05:51:38
β—‹NSns103.ovh.net2017-08-11 β†’ 2017-08-11 Β· 3 obs
● 2017-08-11 06:18:04
β—‹ 2026-02-18 13:25:28
β—‹ 2026-06-21 05:51:38
●NSns2.atom.com2026-02-18 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-08-11 06:18:04
● 2026-02-18 13:25:28
● 2026-06-21 05:51:38
β—‹MXredirect.ovh.net2017-08-11 β†’ 2017-08-11 Β· 3 obs
● 2017-08-11 06:18:04
β—‹ 2026-02-18 13:25:28
β—‹ 2026-06-21 05:51:38
β—‹A164.132.235.172017-08-11 β†’ 2017-08-11 Β· 3 obs
● 2017-08-11 06:18:04
β—‹ 2026-02-18 13:25:28
β—‹ 2026-06-21 05:51:38
β—‹A2001:41d0:301::232017-08-11 β†’ 2017-08-11 Β· 3 obs
● 2017-08-11 06:18:04
β—‹ 2026-02-18 13:25:28
β—‹ 2026-06-21 05:51:38
●A52.20.84.622026-02-18 β†’ 2026-06-21 Β· 3 obs
β—‹ 2017-08-11 06:18:04
● 2026-02-18 13:25:28
● 2026-06-21 05:51:38

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
botchains.comns1.atom.com, ns2.atom.com2 records

βœ… Authoritative Response

Server:50.19.240.86

NS records: ns1.atom.com, ns2.atom.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for botchains.com (unsigned zone)

⏱️ Timing

Total: 106ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A152.20.84.62
NS2ns1.atom.com, ns2.atom.com
TXT1f0095018235b8109a2bf9f65674a1784b6971ed6
SOA1ns1.atom.com hostmaster.botchains.com

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)

Analysis

IP Addresses

botchains.com resolves to just one IP address, 52.20.84.62.

Two other host names, along with postbetter.com, hardrop.com and rnly.com, also share IP numbers with botchains.com.

Name Servers

DNS delegation for botchains.com points to two name servers: ns1.atom.com and ns2.atom.com.

botchains.com shares its NS records with other domains, for example coubt.com, wellsio.com, provebo.com and two others.

At least some of botchains.com's name servers are shared with other domains, for example hexura.com and securescreen.com.

These name servers tend to be used in conjunction with the name servers verification-refeskkalf4qgvebx3uk7a.ns101.verify.hn.

Each of ns1.atom.com and ns2.atom.com has one IP address: ns1.atom.com uses 44.219.81.145 and ns2.atom.com uses 50.19.240.86.