pixelswarm.dev - robtex.com
pixelswarm.dev
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.systemdns.com ⭐ | ||||||
| A | 2604:4000:0:d:216:40:47:90🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns1.systemdns.com | ||||||
| A | 216.40.47.90🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0 | ||||||
| PTR | ns1.systemdns.com | ||||||
| NS | ns2.systemdns.com | ||||||
| A | 2604:4000:2800:d:64:99:148:16🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co. | ||||||
| PTR | ns2.systemdns.com | ||||||
| A | 64.98.148.16🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co. | ||||||
| PTR | ns2.systemdns.com | ||||||
| NS | ns3.systemdns.com | ||||||
| A | 2604:4000:0:d:64:99:96:36🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns3.systemdns.com | ||||||
| A | 64.99.96.36🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2 | ||||||
| PTR | ns3.systemdns.com | ||||||
| SOA | ns1.systemdns.comhostmaster@systemdns.com serial=1790653180 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
pixelswarm.com |
pixelswarm.pages.dev |
pixelswarm.dev |
pixelswarm.co |
pixelswarm.org |
pixelswarm.io |
pixelswarm.net |
pixelswarm.tech |
Similar names
Previous names
Next names
DNS History
3 records (3 active, 0 former)
●NSns1.systemdns.com2026-10-01 → 2026-10-04 · 2 obs
● 2026-10-04 09:57:00
●NSns2.systemdns.com2026-10-01 → 2026-10-04 · 2 obs
● 2026-10-04 09:57:00
●NSns3.systemdns.com2026-10-01 → 2026-10-04 · 2 obs
● 2026-10-04 09:57:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld5.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | 10 records |
| pixelswarm.dev | ns3.systemdns.com, ns2.systemdns.com, ns1.systemdns.com | - |
✅ Authoritative Response
Server:64.98.148.16
NS records: ns3.systemdns.com, ns2.systemdns.com, ns1.systemdns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pixelswarm.dev (unsigned zone)
⏱️ Timing
Total: 722ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns1.systemdns.com, ns3.systemdns.com... |
| SOA | 1 | ns1.systemdns.com hostmaster.systemdns.c |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
The authoritative name servers for pixelswarm.dev are ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com — three in total.
pixelswarm.dev partially shares its NS delegation with several other domains, including 3300ponderosaroad.com, wangxiaoping.net, irrigasol.com and two others.
ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com all resolve to exactly two IP numbers apiece: ns1.systemdns.com → 216.40.47.90 and 2604:4000:0:d:216:40:47:90; ns2.systemdns.com → 64.98.148.16 and 2604:4000:2800:d:64:99:148:16; ns3.systemdns.com → 64.99.96.36 and 2604:4000:0:d:64:99:96:36.