trafficlegend.com - robtex.com
trafficlegend.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@trafficlegend.com 2025-11-10 #1 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1771291435 | ||||||
Same first word
trafficlegend.com |
Similar names
🔍 DNS Trace
Analysis
IP Addresses
trafficlegend.com resolves to one IP number: 52.20.84.62.
Other host names, for instance netalyze.com, sweetchefs.com, xvmd.com, fantasyhack.com and teenchef.com share IP numbers with trafficlegend.com.
Name Servers
trafficlegend.com's delegation uses two name servers: ns1.atom.com and ns2.atom.com.
trafficlegend.com uses the same name server setup as other domains, such as jpnd.net, ollop.com, aegific.com, ijira.com and websible.com.
trafficlegend.com at least partially shares name servers with other domains, for instance koporo.com, inceptary.com, codeexpert.org and sentdata.com.
These name servers are often used with ns1.namebrightdns.com and ns2.namebrightdns.com.
Host names with a single IP address: ns1.atom.com points to 44.219.81.145; ns2.atom.com points to 50.19.240.86.