pixelclone.cloud - robtex.com
pixelclone.cloud
cloud
| 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=1795271429 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
βNSns1hwy.name.com2026-10-03 β 2026-11-21 Β· 2 obs
β 2026-11-21 15:31:44
βNSns2fln.name.com2026-10-03 β 2026-11-21 Β· 2 obs
β 2026-11-21 15:31:44
βNSns3fqs.name.com2026-10-03 β 2026-11-21 Β· 2 obs
β 2026-11-21 15:31:44
βNSns4jnz.name.com2026-10-03 β 2026-11-21 Β· 2 obs
β 2026-11-21 15:31:44
βA185.158.133.12026-10-03 β 2026-11-21 Β· 2 obs
β 2026-11-21 15:31:44
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | 8 records |
| pixelclone.cloud | ns1hwy.name.com, ns2fln.name.com, ns3fqs.name.com, ns4jnz.name.com | - |
β Authoritative Response
Server:163.114.216.17
NS records: ns1hwy.name.com, ns2fln.name.com, ns3fqs.name.com, ns4jnz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)
β±οΈ Timing
Total: 1033ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.158.133.1 |
| NS | 4 | ns1hwy.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)
Analysis
IP Addresses
pixelclone.cloud resolves to just one IP address, 185.158.133.1.
Two other host names, along with lifinia.com, olheiro.co and metawatt.io, also share IP numbers with pixelclone.cloud.
Name Servers
pixelclone.cloud delegates to five name servers: ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
At least some of pixelclone.cloud's name servers are shared with other domains, for example almukaabbuildcont.app, vadimgrushin.dev, minglemesh.com and two more.
These name servers tend to co-occur with ns3fqs.name.com, ns4jnz.name.com, ns3bfm.name.com and 5 other name servers in the same DNS delegations.
Host names that have two IP addresses:
ns1.name.com points to 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com points to 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com points to 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com points to 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.name.com points to 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com and ns1hwy.name.com are host names that each point to 2a00:edc0:107::1 IP addresses.
ns1.name.com and ns1hwy.name.com are host names that each point to 163.114.216.17 IP addresses.