techrecon.com - dns.ninja
techrecon.com
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=1781359438 | ||||||
Same first word
Similar names
DNS History
10 records (6 active, 4 former)
●NSns1.name.com2026-03-05 → 2026-06-13 · 3 obs
● 2026-03-05 14:06:08
● 2026-06-13 14:18:18
○NSns1bdg.domainsite.com2015-07-18 → 2017-03-31 · 4 obs
● 2017-03-31 14:54:18
○ 2026-03-05 14:06:08
○ 2026-06-13 14:18:18
●NSns1bdg.name.com2026-03-05 → 2026-06-13 · 3 obs
● 2026-03-05 14:06:08
● 2026-06-13 14:18:18
○NSns2fgv.domainsite.com2015-07-18 → 2017-03-31 · 4 obs
● 2017-03-31 14:54:18
○ 2026-03-05 14:06:08
○ 2026-06-13 14:18:18
●NSns2fgv.name.com2026-03-05 → 2026-06-13 · 3 obs
● 2026-03-05 14:06:08
● 2026-06-13 14:18:18
○NSns3jmt.domainsite.com2015-07-18 → 2017-03-31 · 4 obs
● 2017-03-31 14:54:18
○ 2026-03-05 14:06:08
○ 2026-06-13 14:18:18
●NSns3jmt.name.com2026-03-05 → 2026-06-13 · 3 obs
● 2026-03-05 14:06:08
● 2026-06-13 14:18:18
○NSns4cfn.domainsite.com2015-07-18 → 2017-03-31 · 4 obs
● 2017-03-31 14:54:18
○ 2026-03-05 14:06:08
○ 2026-06-13 14:18:18
●NSns4cfn.name.com2026-03-05 → 2026-06-13 · 3 obs
● 2026-03-05 14:06:08
● 2026-06-13 14:18:18
●A70.147.97.2032015-07-18 → 2026-06-13 · 2 obs
● 2026-06-13 14:18:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net... | - |
| techrecon.com | ns1bdg.name.com, ns2fgv.name.com, ns3jmt.name.com, ns4cfn.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1bdg.name.com, ns2fgv.name.com, ns3jmt.name.com, ns4cfn.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for techrecon.com (unsigned zone)
⏱️ Timing
Total: 143ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 70.147.97.203 |
| NS | 4 | ns1bdg.name.com, ns2fgv.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1bdg.name.com, ns1bdg.name.com, ns2fgv.name.com...)
Analysis
IP Addresses
techrecon.com resolves to just one IP address, 70.147.97.203.
Host names like adsl-070-147-097-203.sip.mco.bellsouth.net are further examples that share IP numbers with techrecon.com.
Name Servers
techrecon.com delegates to five name servers: ns1.name.com, ns1bdg.name.com, ns2fgv.name.com and two others.
At least some of techrecon.com's name servers are shared with other domains, for example midgetcity.net, celuce.com, qy7688.com and two more.
These name servers tend to co-occur with ns3jmt.name.com, ns4cfn.name.com, ns2kry.name.com and 7 other name servers in the same DNS delegations.
Host names that have two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1bdg.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2fgv.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3jmt.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4cfn.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1bdg.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1bdg.name.com each resolve to 163.114.216.17 IP addresses.