idmapp.com - dns.ninja
idmapp.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=1785951804 | ||||||
Same first word
idmapp.com |
Similar names
DNS History
11 records (11 active, 0 former)
βNSns1.name.com2026-04-25 β 2026-08-05 Β· 3 obs
β 2026-04-25 10:55:38
β 2026-08-05 17:56:30
βNSns1dns.name.com2017-11-23 β 2026-08-05 Β· 2 obs
β 2026-08-05 17:56:30
βNSns2fjz.name.com2017-11-23 β 2026-08-05 Β· 2 obs
β 2026-08-05 17:56:30
βNSns3fgh.name.com2017-11-23 β 2026-08-05 Β· 2 obs
β 2026-08-05 17:56:30
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| idmapp.com | ns1dns.name.com, ns2fjz.name.com, ns3fgh.name.com, ns4clq.name.com | 8 records |
β Authoritative Response
Server:163.114.216.17
NS records: ns1dns.name.com, ns2fjz.name.com, ns3fgh.name.com, ns4clq.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for idmapp.com (unsigned zone)
β±οΈ Timing
Total: 273ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1dns.name.com, ns2fjz.name.com... |
| MX | 6 | mx3.name.com (pri: 20), mx4.name.com (pri: 50)... |
| TXT | 1 | v=spf1 a mx ~all |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1dns.name.com, ns1dns.name.com, ns2fjz.name.com...)
Analysis
Name Servers
idmapp.com delegates to five name servers: ns1.name.com, ns1dns.name.com, ns2fjz.name.com and two others.
idmapp.com has at least partial name server overlap with other domains, such as tydus.org, lushfun.com, thejordanlivestock.net and two others.
ns4clq.name.com, ns3fgh.name.com and ns3gmt.name.com β plus 7 other name servers β are commonly paired with these name servers.
Host names that have two IP addresses:
ns1.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns1dns.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns2fjz.name.com resolves to 163.114.216.49 and 2402:cf80:107::1.
ns3fgh.name.com resolves to 163.114.217.17 and 2a00:edc0:107::49.
ns4clq.name.com resolves to 163.114.217.49 and 2402:cf80:107::49.
The host names ns1.name.com and ns1dns.name.com both resolve to 2a00:edc0:107::1 IP addresses.
The host names ns1.name.com and ns1dns.name.com both resolve to 163.114.216.17 IP addresses.
Mail Servers
Mail for idmapp.com is routed through 6 mail servers, including mx3.name.com, mx4.name.com, mx5.name.com and 3 other.
There is at least a partial MX overlap between idmapp.com and other domains, including freecamsly.com, omhub.us, onlinediet.net and two others.
These mail servers tend to appear together with the mail servers mx6.name.com, mx7.name.com and mx8.name.com.
Host names that point to one IP address:
mx3.name.com resolves to 173.192.7.98.
mx4.name.com resolves to 173.192.7.99.
mx5.name.com resolves to 173.192.7.100.
mx6.name.com resolves to 173.192.7.101.
mx7.name.com resolves to 173.192.7.102.
mx8.name.com resolves to 173.192.7.103.