tinyforge.app - robtex.com
tinyforge.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
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A185.158.133.12026-09-27 → 2026-11-11 · 2 obs
● 2026-11-11 02:02:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| app | ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| tinyforge.app | ns1hwy.name.com, ns3fqs.name.com, ns2fln.name.com, ns4jnz.name.com | - |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1hwy.name.com, ns3fqs.name.com, ns2fln.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: 394ms | 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
tinyforge.app has exactly one IP address — 185.158.133.1.
intelligistica.net, insideedge.in, agentic-x.de plus two other host names have IP numbers in common with tinyforge.app.
Name Servers
Five name servers handle delegation for tinyforge.app: ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
tinyforge.app shares at least some of its name servers with other domains, including trustedhealthquote.com, mimomulti.app, velocityrealestatesolutions.com and two others.
These name servers are frequently seen alongside ns4jnz.name.com, ns3fqs.name.com, ns1bqx.name.com and 7 other name servers.
Host names pointing 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.
ns3fqs.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.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.