indyfencing.com - dns.ninja
indyfencing.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.233.30.191🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix | ||||||
| PTR | ns2.namepros-dns.com | ||||||
| NS | ns1.namepros-dns.com ⭐ | ||||||
| A | 54.237.57.21🇺🇸 Amazon54.237.0.0/16 EC2 IAD prefix | ||||||
| PTR | ns1.namepros-dns.com | ||||||
| NS | bdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is ⚠️ Not in zone NS records | ||||||
| A | 3.233.30.191🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix | ||||||
| PTR | ns2.namepros-dns.com | ||||||
| NS | ns2.bdz3686s2h3d83pbbr598zhd.ns.namepros-dns.is ⚠️ Not in parent delegation | ||||||
| A | 3.233.30.191🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix | ||||||
| PTR | ns2.namepros-dns.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.namepros-dns.comdns@namepros.com serial=15033674 | ||||||
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=1786293679 | ||||||
Same first word
indyfencing.com |
DNS History
16 records (4 active, 12 former)
●NSbdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is2026-05-23 → 2026-08-09 · 3 obs
● 2026-05-23 04:13:50
● 2026-08-09 17:12:14
○NSns1.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
●NSns1.namepros-dns.com2026-05-23 → 2026-08-09 · 3 obs
● 2026-05-23 04:13:50
● 2026-08-09 17:12:14
●NSns2.bdz3686s2h3d83pbbr598zhd.ns.namepros-dns.is2026-05-23 → 2026-08-09 · 3 obs
● 2026-05-23 04:13:50
● 2026-08-09 17:12:14
○NSns2.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○NSns3.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○NSns4.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○MXmx1soho25.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○MXmx2soho25.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○MXmx3soho25.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○MXmx4soho25.carrierzone.com2015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
○A199.59.243.2282026-05-23 → 2026-08-09 · 2 obs
○ 2026-08-09 17:12:14
●A3.233.30.1912026-05-23 → 2026-08-09 · 3 obs
● 2026-05-23 04:13:50
● 2026-08-09 17:12:14
○A64.29.145.152015-06-08 → 2016-04-09 · 4 obs
● 2016-04-09 13:36:50
○ 2026-05-23 04:13:50
○ 2026-08-09 17:12:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| indyfencing.com | ns1.namepros-dns.com, bdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is | 1 record |
✅ Authoritative Response
Server:54.237.57.21
NS records: ns1.namepros-dns.com, bdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for indyfencing.com (unsigned zone)
⏱️ Timing
Total: 2301ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.233.30.191 |
| NS | 2 | ns1.namepros-dns.com, ns2.bdz3686s2h3d83pbbr598zhd.ns.namepros |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.namepros-dns.com dns.namepros.com |
📌 Glue Records Collected
Total: 1
Out-of-bailiwick: 1 (ns1.namepros-dns.com)
Analysis
IP Addresses
indyfencing.com points to a single IP number: 3.233.30.191.
Additional host names — bykl.com, shortnumber1.dnsg.net, lb.linkbuilderpro.com and two others — share IP numbers with indyfencing.com.
Name Servers
DNS for indyfencing.com is handled by three authoritative name servers: ns1.namepros-dns.com, bdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is and ns2.bdz3686s2h3d83pbbr598zhd.ns.namepros-dns.is.
indyfencing.com has at least partial name server overlap with other domains, such as nashville.co, refa.co, ftmyersroofing.com and two others.
ns2.abdulbasit.ns.namepros-dns.is, ns2.f5f895r3r6zmmpsm2h92.ns.namepros-dns.is and zss5p6352r53spzb3phzhs8pdh6583j8.ns.namepros-dns.is — plus 7 other name servers — are commonly paired with these name servers.
Three hosts, each with one IP address: ns1.namepros-dns.com → 54.237.57.21; bdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is → 3.233.30.191; ns2.bdz3686s2h3d83pbbr598zhd.ns.namepros-dns.is → 3.233.30.191.
Host names pointing to 3.233.30.191 IP addresses: bdz3686s2h3d83pbbr598zhd25b8ff6b.ns.namepros-dns.is and ns2.bdz3686s2h3d83pbbr598zhd.ns.namepros-dns.is.