CF1757913008890-tsm20250914164358

WWW.ROBTEX.COM - token.red

Search for IP or hostnames:

token.red checked at 2025-09-15T05:10:08.875Z 177ms 96/96/96 100% R:15

token.red

MX.
NSns1.afternic.com
A2603:5:2126::45🇺🇸 GODADDY-DNS
PTRns1.afternic.com
A97.74.98.69🇺🇸 GODADDY-DNS
PTRns1.afternic.com
NSns2.afternic.com
A2603:5:2226::45🇺🇸 GODADDY-DNS
PTRns2.afternic.com
A173.201.66.69🇺🇸 GODADDY-DNS
PTRns2.afternic.com
A99.83.161.153🇺🇸 Amazon
PTRa2b7bf3398455f345.awsglobalaccelerator.com
A166.117.110.61🇺🇸 Amazon

red

NSa0.nic.red
NSa2.nic.red
NSb0.nic.red
NSc0.nic.red

Starts with same word

Starts similarily

AI analysis

There are two IP numbers that token.red points to: 99.83.161.153 and 166.117.110.61.

IP numbers are shared between token.red and other host names such as redcorp.us, aiveb.com, supprimer.org, www.bled.pro, and abhaysopori.com.

Two name servers, ns1.afternic.com and ns2.afternic.com, have been delegated for token.red.

Other domains like nubalife.com, dix.tech, mvelo.com, seksbox.com, and mbut.com, share the same name server setup as token.red.

ns1.afternic.com and ns2.afternic.com both point to two IP numbers each: 2603:5:2126::45, 97.74.98.69 for ns1.afternic.com and 2603:5:2226::45, 173.201.66.69 for ns2.afternic.com.

The mail server, ., is responsible for handling token.red.

Just like domains such as blah.42.123.doesntwork.com, battlesim.com, udiconsulting.com, ipower.pro, and hostmaster.buyshack.com, token.red also shares the same mail server setup.

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

JpySCPo CF johedugfp 2025-09-15