remotelyfound.com - dns.ninja
remotelyfound.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 76.76.21.21🇺🇸 Amazon76.76.21.0/24 EC2 Prefix | ||||||
| NS | remotelyfound.com ⭐ | ||||||
| A | 76.76.21.21🇺🇸 Amazon76.76.21.0/24 EC2 Prefix | ||||||
| NS | ns3.my-ndns.com | ||||||
| A | 154.85.54.43🇺🇸 BAIDU-1154.85.48.0/21 AS55967 | ||||||
| NS | ns4.my-ndns.com | ||||||
| A | 43.162.114.218🇺🇸 TENCENT-NET-AP-CN43.162.112.0/20 ACEVILLE PTE.LTD. 16 COLLYER QUAY 18-29 INCOME AT RAFFLES | ||||||
| SOA | remotelyfound.comroot@remotelyfound.com 2025-02-16 #0 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785567127 | ||||||
NS for
remotelyfound.com |
Same first word
remotelyfound.com |
DNS History
4 records (4 active, 0 former)
●NSns3.my-ndns.com2026-07-24 → 2026-08-01 · 2 obs
● 2026-08-01 07:11:06
●NSns4.my-ndns.com2026-07-24 → 2026-08-01 · 2 obs
● 2026-08-01 07:11:06
●NSremotelyfound.com2026-07-24 → 2026-08-01 · 2 obs
● 2026-08-01 07:11:06
●A76.76.21.212026-07-24 → 2026-08-01 · 2 obs
● 2026-08-01 07:11:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| remotelyfound.com | ns3.my-ndns.com, ns4.my-ndns.com | 2 records |
✅ Authoritative Response
Server:154.85.54.43
NS records: ns3.my-ndns.com, ns4.my-ndns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for remotelyfound.com (unsigned zone)
⏱️ Timing
Total: 485ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 76.76.21.21 |
| NS | 2 | ns3.my-ndns.com, ns4.my-ndns.com |
| SOA | 1 | remotelyfound.com root.remotelyfound.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns3.my-ndns.com, ns4.my-ndns.com)
Analysis
Name Server Role
The NS records for remotelyfound.com point back to remotelyfound.com itself.
ns3.my-ndns.com and ns4.my-ndns.com frequently appear as name servers alongside remotelyfound.com.
IP Addresses
remotelyfound.com resolves to just one IP address, 76.76.21.21.
Two other host names, along with cleveland-theater.com, ironmountain.com.pe and gwcd.org, also share IP numbers with remotelyfound.com.
Name Servers
Three name servers handle the delegation for remotelyfound.com: remotelyfound.com, ns3.my-ndns.com and ns4.my-ndns.com.
remotelyfound.com shares at least some of its name servers with other domains, including smartportal-coinbase.com, dfs-homes.com, cucumbernonsense.com and two others.
The hostnames remotelyfound.com, ns3.my-ndns.com and ns4.my-ndns.com each resolve to a single IP: remotelyfound.com → 76.76.21.21, ns3.my-ndns.com → 154.85.54.43, ns4.my-ndns.com → 43.162.114.218.