hmulji.app - robtex.com
hmulji.app
app
| 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=101427 | ||||||
Same first word
hmulji.app |
DNS History
6 records (6 active, 0 former)
●A185.158.133.12026-08-13 → 2026-08-15 · 2 obs
● 2026-08-15 20:13:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| app | ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | - |
| hmulji.app | ns2fln.name.com, ns4jnz.name.com, ns3fqs.name.com, ns1hwy.name.com | - |
✅ Authoritative Response
Server:163.114.216.49
NS records: ns2fln.name.com, ns4jnz.name.com, ns3fqs.name.com, ns1hwy.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hmulji.app (unsigned zone)
⏱️ Timing
Total: 694ms | 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 |
Analysis
IP Addresses
hmulji.app points to a single IP number: 185.158.133.1.
Additional host names — lookupthebook.com, blockchainsettlers.com, (0x6675636b)iwishiknewth.at and two others — share IP numbers with hmulji.app.
Name Servers
Delegation for hmulji.app is to five name servers: ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
There is at least partial name server overlap between hmulji.app and other domains — webpain.com, z2788fu3j3.com, artevolution.net and two more among them.
These name servers regularly appear alongside ns4jnz.name.com, ns3fqs.name.com, ns1cnb.name.com and 7 other name servers in NS record sets.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1hwy.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1hwy.name.com resolve to 163.114.216.17 IP addresses each.