midloop.studio - robtex.com
midloop.studio
studio
| DNSSEC | π Signed (DS record present) | ||||||
| NS | v0n0.nic.studio β | ||||||
| NS | v0n1.nic.studio | ||||||
| NS | v0n2.nic.studio | ||||||
| NS | v0n3.nic.studio | ||||||
| NS | v2n0.nic.studio | ||||||
| NS | v2n1.nic.studio | ||||||
| SOA | v0n0.nic.studiohostmaster@donuts.email serial=1794579921 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
6 records (5 active, 1 former)
βNSns1hwy.name.com2026-09-23 β 2026-11-13 Β· 2 obs
β 2026-11-13 14:53:46
βNSns2fln.name.com2026-09-23 β 2026-11-13 Β· 2 obs
β 2026-11-13 14:53:46
βNSns3bgq.name.com2026-09-23 β 2026-11-13 Β· 2 obs
β 2026-11-13 14:53:46
βNSns4ghm.name.com2026-09-23 β 2026-11-13 Β· 2 obs
β 2026-11-13 14:53:46
βA91.195.240.942026-09-23 β 2026-09-23 Β· 3 obs
β 2026-11-13 14:53:44
β 2026-11-13 14:53:46
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| studio | v2n0.nic.studio, v0n2.nic.studio, v0n0.nic.studio, v0n3.nic.studio... | 12 records |
| midloop.studio | ns3bgq.name.com, ns4ghm.name.com, ns1hwy.name.com, ns2fln.name.com | - |
β Authoritative Response
Server:163.114.216.49
NS records: ns3bgq.name.com, ns4ghm.name.com, ns1hwy.name.com, ns2fln.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for midloop.studio (unsigned zone)
β±οΈ Timing
Total: 631ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1hwy.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 12
In-bailiwick: 12 (v2n0.nic.studio, v2n0.nic.studio, v0n2.nic.studio...)
Analysis
Name Servers
midloop.studio has five name servers, which are ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
midloop.studio has at least partial name server overlap with other domains, such as jajunote.app, lanzhouloyalty.com, neuroarena.ai and two others.
ns4jnz.name.com, ns3fqs.name.com and ns4ghm.name.com β plus 7 other name servers β are commonly paired with these name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3bgq.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4ghm.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1hwy.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1hwy.name.com each resolve to 163.114.216.17 IP addresses.