CF1757719567148-tsm20250912070358

IPLIST.NET - traffic.to

Search for IP or hostnames:

traffic.to checked at 2025-09-12T23:26:07.104Z 678ms 66/66/66 100% R:9

traffic.to

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

to

NSns01.trs-dns.com
NSns10.trs-dns.info
NSns01.trs-dns.net
NSns10.trs-dns.org

Starts with same word

Starts similarily

AI analysis

traffic.to points to two IP numbers: 99.83.161.153 and 166.117.110.61.

IP numbers are shared between traffic.to and other host names, such as dynawin.com, 86.233.199.layerdns.com, meganta.com, satoshi2.xyz, and ticket.guide.

Two name servers, ns1.afternic.com and ns2.afternic.com, are assigned the delegation of traffic.to.

Other domains, such as rxq.me, skilts.com, vtyl.com, duralize.com, and pulsetrax.com, share the same name server setup as traffic.to.

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, ., handles traffic.to.

The mail server setup of traffic.to matches with other domains such as vkk.co, 188.196.161.layerdns.com, dns.studio212.com, eglobalco.com, and hwww.vantige.com.

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

OpbkvPw CF johedugfp 2025-09-12