dispatch.bot - robtex.com

πŸ›‘οΈDomain Reputation CheckBlocklist, phishing & malware statusβ†’

dispatch.bot

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
SOAns1.atom.comhostmaster@dispatch.bot 2025-03-20 #3

bot

DNSSECπŸ”’ Signed (DS record present)
NSdns1.nic.bot ⭐
NSdns2.nic.bot
NSdns3.nic.bot
NSdns4.nic.bot
NSdnsa.nic.bot
NSdnsb.nic.bot
NSdnsc.nic.bot
NSdnsd.nic.bot
TXT#Timestamp: 1787627400
SOAdns1.nic.bothostmaster@nominet.org.uk serial=1787626819

Previously MX for

Same first word

Similar names

Previous names

Next names

DNS History

7 records (3 active, 4 former)

202120222023202420252026NSns1.atom.comns2.atom.comns1.trucker101.comns2.trucker101.comMXdispatch.botA52.20.84.6272.55.133.164
●NSns1.atom.com2026-08-23 β†’ 2026-08-25 Β· 3 obs
β—‹ 2020-03-28 12:28:22
● 2026-08-23 02:24:22
● 2026-08-25 03:21:16
β—‹NSns1.trucker101.com2020-03-28 β†’ 2020-03-28 Β· 3 obs
● 2020-03-28 12:28:22
β—‹ 2026-08-23 02:24:22
β—‹ 2026-08-25 03:21:16
●NSns2.atom.com2026-08-23 β†’ 2026-08-25 Β· 3 obs
β—‹ 2020-03-28 12:28:22
● 2026-08-23 02:24:22
● 2026-08-25 03:21:16
β—‹NSns2.trucker101.com2020-03-28 β†’ 2020-03-28 Β· 3 obs
● 2020-03-28 12:28:22
β—‹ 2026-08-23 02:24:22
β—‹ 2026-08-25 03:21:16
β—‹MXdispatch.bot2020-03-28 β†’ 2020-03-28 Β· 3 obs
● 2020-03-28 12:28:22
β—‹ 2026-08-23 02:24:22
β—‹ 2026-08-25 03:21:16
●A52.20.84.622026-08-23 β†’ 2026-08-25 Β· 3 obs
β—‹ 2020-03-28 12:28:22
● 2026-08-23 02:24:22
● 2026-08-25 03:21:16
β—‹A72.55.133.1642020-03-28 β†’ 2020-03-28 Β· 3 obs
● 2020-03-28 12:28:22
β—‹ 2026-08-23 02:24:22
β—‹ 2026-08-25 03:21:16

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
botdns2.nic.bot, dnsa.nic.bot, dns4.nic.bot, dns1.nic.bot...15 records
dispatch.botns1.atom.com, ns2.atom.com-

βœ… Authoritative Response

Server:50.19.240.86

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dispatch.bot (unsigned zone)

⏱️ Timing

Total: 1425ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A152.20.84.62
NS2ns1.atom.com, ns2.atom.com
SOA1ns1.atom.com hostmaster.dispatch.bot

πŸ“Œ Glue Records Collected

Total: 15

In-bailiwick: 15 (dns1.nic.bot, dns2.nic.bot, dns3.nic.bot...)

Analysis

IP Addresses

dispatch.bot resolves to one IP address: 52.20.84.62.

populi.org, presig.com, flywisp.com and two other host names share IP numbers with dispatch.bot.

Name Servers

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

dispatch.bot uses the same name servers as several other domains β€” among them mohaku.com, musegroove.com, vishalindustries.com and two more.

There is at least partial name server overlap between dispatch.bot and other domains β€” ghrob.com, xer0x.com, disruptif.com and two more among them.

These name servers are routinely deployed together with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.

ns1.atom.com β†’ 44.219.81.145 and ns2.atom.com β†’ 50.19.240.86: one IP number per host name.