infected.bot - robtex.com

infected.bot

DNSSEC⚠️ Not signed
NSlaunch1.spaceship.net ⚠️ Not in zone NS records
A2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSlaunch2.spaceship.net ⚠️ Not in zone NS records
A2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US

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
SOAdns1.nic.bothostmaster@nominet.org.uk serial=1775981382

Same first word

infected.be
infected.ca
infected.computer
infected.no
infected.host
infected.cat
infected.io
infected.ru
infected.gr
infected.us
infected.markets
infected.info
infected.in
infected.email
infected.bot
infected.hu
infected.org
infected.house
infected.digital
infected.systems
infected.it
infected.market
infected.dk
infected.co.il
infected.com.ar
infected.org.uk
infected.co
infected.me
infected.de
infected.com

Similar names

defentic.com
cdtenfei.com
fcedinet.md
decentfi.com
deficent.xyz
ifencedt.com
fencedit.com

DNS History

8 records (2 active, 6 former)

NSlaunch1.spaceship.netlaunch2.spaceship.netian.ns.cloudflare.comoaklyn.ns.cloudflare.comA104.21.76.217172.67.201.672606:4700:3031::ac43:c9432606:4700:3036::6815:4cd9
○NSian.ns.cloudflare.com2026-03-31 → 2026-04-07 · 3 obs
● 2026-03-31 22:30:22
● 2026-04-07 16:01:18
○ 2026-04-12 08:15:16
●NSlaunch1.spaceship.net2026-04-12 → 2026-04-12 · 2 obs
○ 2026-04-07 16:01:18
● 2026-04-12 08:15:16
●NSlaunch2.spaceship.net2026-04-12 → 2026-04-12 · 2 obs
○ 2026-04-07 16:01:18
● 2026-04-12 08:15:16
○NSoaklyn.ns.cloudflare.com2026-03-31 → 2026-04-07 · 3 obs
● 2026-03-31 22:30:22
● 2026-04-07 16:01:18
○ 2026-04-12 08:15:16
○A104.21.76.2172026-03-31 → 2026-04-07 · 3 obs
● 2026-03-31 22:30:22
● 2026-04-07 16:01:18
○ 2026-04-12 08:15:16
○A172.67.201.672026-03-31 → 2026-04-07 · 3 obs
● 2026-03-31 22:30:22
● 2026-04-07 16:01:18
○ 2026-04-12 08:15:16
○A2606:4700:3031::ac43:c9432026-03-31 → 2026-04-07 · 3 obs
● 2026-03-31 22:30:22
● 2026-04-07 16:01:18
○ 2026-04-12 08:15:16
○A2606:4700:3036::6815:4cd92026-03-31 → 2026-04-07 · 3 obs
● 2026-03-31 22:30:22
● 2026-04-07 16:01:18
○ 2026-04-12 08:15:16

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
botdnsb.nic.bot, dnsd.nic.bot, dns4.nic.bot, dns2.nic.bot...16 records
infected.botlaunch1.spaceship.net, launch2.spaceship.net-

✅ Authoritative Response

Server:162.159.27.32

NS records: launch1.spaceship.net, launch2.spaceship.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for infected.bot (unsigned zone)

⏱️ Timing

Total: 567ms | Queries: -

📄 Records

TypeCountSample Data

📌 Glue Records Collected

Total: 16

In-bailiwick: 16 (dnsb.nic.bot, dnsb.nic.bot, dnsd.nic.bot...)

Analysis

Name Servers

infected.bot's delegation uses two name servers, launch1.spaceship.net and launch2.spaceship.net.

infected.bot shares the same name server setup as other domains, for example tbmp.com, tisday.com, prodear.com, yugae.com and coventryhomes.co.uk.

Host names with two IPs:

launch1.spaceship.net points to: 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38

launch2.spaceship.net points to: 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32