CF1761175127147-tsm20251017082432

MXLIST.NET - traffic.to

Search for IP or hostnames:

traffic.to checked at 2025-10-22T23:18:47.129Z 116ms 66/66/66 100% R:10

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
A13.248.169.48🇺🇸 Amazon
PTRa904c694c05102f30.awsglobalaccelerator.com
A76.223.54.146🇺🇸 Amazon
PTRa904c694c05102f30.awsglobalaccelerator.com

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 IPs: 13.248.169.48 and 76.223.54.146.

Other host names, for instance malware.meatpounder.com, dynawin.com, fogyyoga.com, hostmaster.yourcost.com and 86.233.199.layerdns.com share IP numbers with traffic.to.

Two name servers ns1.afternic.com and ns2.afternic.com are delegated to traffic.to.

traffic.to uses the same name server configuration as other domains, such as rxq.me, vtyl.com, duralize.com, pulsetrax.com and kiiwi.com.

Host names with two IPs:

ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69.

ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69.

traffic.to is handled by a single mail server, ..

traffic.to shares the same mail server setup as other domains, including 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

qKZKEAe CF johedugfp 2025-10-22