toxic.pw - robtex.com
toxic.pw
| 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@toxic.pw 2026-06-09 #3 | ||||||
pw
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1785983029 | ||||||
⚠️ On DNS blocklist: spam-tlds
Previously MX for
toxic.pw |
Same first word
Similar names
DNS History
12 records (3 active, 9 former)
○NSdns1.registrar-servers.com2015-08-19 → 2026-02-15 · 4 obs
● 2026-02-15 13:11:20
○ 2026-03-16 16:32:02
○ 2026-08-06 02:34:24
○NSdns2.registrar-servers.com2015-08-19 → 2026-02-15 · 4 obs
● 2026-02-15 13:11:20
○ 2026-03-16 16:32:02
○ 2026-08-06 02:34:24
○NSdns3.registrar-servers.com2015-08-19 → 2016-06-13 · 4 obs
● 2016-06-13 06:44:28
○ 2016-07-12 01:14:32
○ 2026-08-06 02:34:24
○NSdns4.registrar-servers.com2015-08-19 → 2016-06-13 · 4 obs
● 2016-06-13 06:44:28
○ 2016-07-12 01:14:32
○ 2026-08-06 02:34:24
○NSdns5.registrar-servers.com2015-08-19 → 2016-06-13 · 4 obs
● 2016-06-13 06:44:28
○ 2016-07-12 01:14:32
○ 2026-08-06 02:34:24
●NSns1.atom.com2026-06-24 → 2026-08-06 · 3 obs
● 2026-06-24 09:34:54
● 2026-08-06 02:34:24
●NSns2.atom.com2026-06-24 → 2026-08-06 · 3 obs
● 2026-06-24 09:34:54
● 2026-08-06 02:34:24
○MXmail.toxic.pw2015-08-19 → 2026-02-15 · 4 obs
● 2026-02-15 13:11:20
○ 2026-03-16 16:32:02
○ 2026-08-06 02:34:24
○MXsmtp.toxic.pw2015-08-19 → 2026-02-15 · 4 obs
● 2026-02-15 13:11:20
○ 2026-03-16 16:32:02
○ 2026-08-06 02:34:24
○MXtoxic.pw2015-08-19 → 2026-02-15 · 4 obs
● 2026-02-15 13:11:20
○ 2026-03-16 16:32:02
○ 2026-08-06 02:34:24
○A23.92.65.2022015-08-19 → 2026-02-15 · 4 obs
● 2026-02-15 13:11:20
○ 2026-03-16 16:32:02
○ 2026-08-06 02:34:24
●A52.20.84.622026-06-24 → 2026-08-06 · 3 obs
● 2026-06-24 09:34:54
● 2026-08-06 02:34:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pw | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | 8 records |
| toxic.pw | ns1.atom.com, ns2.atom.com | - |
✅ Authoritative Response
Server:50.19.240.86
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for toxic.pw (unsigned zone)
⏱️ Timing
Total: 266ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.toxic.pw |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)
Analysis
IP Addresses
toxic.pw has exactly one IP address — 52.20.84.62.
thinner.me, copyservice.net, relaydesk.com plus two other host names have IP numbers in common with toxic.pw.
Name Servers
toxic.pw is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
The name server configuration of toxic.pw is shared with other domains, for instance astrometa.com, oxa.ca, jamcreate.com and two others.
The name servers for toxic.pw are at least partly shared with other domains such as zipui.com, wenoh.com, mubdy.com and flexydrive.com.
It is common to see these name servers used together with name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn and ns3.verification-eom9svudaqr8s6pbjmubxn.ns101.verify.hn.
ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.