netappteam.com - dns.ninja
netappteam.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=1782542055 | ||||||
Same first word
netappteam.com |
netappteam.de |
Similar names
DNS History
9 records (8 active, 1 former)
●NSns1.netnames.net2015-07-24 → 2026-06-27 · 2 obs
● 2026-06-27 06:41:16
●NSns2.netnames.net2015-07-24 → 2026-06-27 · 2 obs
● 2026-06-27 06:41:16
●NSns5.netnames.net2015-07-24 → 2026-06-27 · 2 obs
● 2026-06-27 06:41:16
●NSns6.netnames.net2015-07-24 → 2026-06-27 · 2 obs
● 2026-06-27 06:41:16
●MXrelay1.netnames.net2015-07-24 → 2026-06-27 · 2 obs
● 2026-06-27 06:41:16
●MXrelay2.netnames.net2015-07-24 → 2026-06-27 · 2 obs
● 2026-06-27 06:41:16
●A165.160.13.202020-04-10 → 2026-06-27 · 3 obs
● 2020-04-10 05:18:24
● 2026-06-27 06:41:16
●A165.160.15.202020-04-10 → 2026-06-27 · 3 obs
● 2020-04-10 05:18:24
● 2026-06-27 06:41:16
○A185.26.230.1292015-07-24 → 2017-04-03 · 4 obs
● 2017-04-03 02:03:12
○ 2020-04-10 05:18:24
○ 2026-06-27 06:41:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| netappteam.com | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | - |
✅ Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for netappteam.com (unsigned zone)
⏱️ Timing
Total: 599ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.15.20, 165.160.13.20 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
Analysis
IP Addresses
netappteam.com points to the IP addresses 165.160.13.20 and 165.160.15.20
Among the host names that share IP numbers with netappteam.com are fillervegetal.fr, truestlending.net, h3-80.gulf.ca and two others.
Name Servers
The domain netappteam.com is delegated to these four name servers: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
The name servers of netappteam.com overlap at least partially with those of other domains — among them rothenberger.cl, assurance-boulogne-billancourt.fr, yellseo.com and two more.
These name servers commonly appear alongside the name servers ns7.netnames.net and ns8.netnames.net.
The four hosts ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net each point to two IP numbers. ns1.netnames.net directs to 156.154.130.100 and 2610:a1:1022::100; ns2.netnames.net directs to 156.154.131.100 and 2610:a1:1023::100; ns5.netnames.net directs to 156.154.130.100 and 2610:a1:1022::100; ns6.netnames.net directs to 156.154.131.100 and 2610:a1:1023::100.
ns1.netnames.net and ns5.netnames.net each have 2610:a1:1022::100 IP addresses.
ns1.netnames.net and ns5.netnames.net each have 156.154.130.100 IP addresses.
ns2.netnames.net and ns6.netnames.net each have 2610:a1:1023::100 IP addresses.
ns2.netnames.net and ns6.netnames.net each have 156.154.131.100 IP addresses.
Mail Servers
The MX records for netappteam.com point to two mail servers: relay1.netnames.net and relay2.netnames.net.
netappteam.com has the same mail server arrangement as a number of other domains, for example mcrew.fr, cision.us, spinecare.nl and two more.
netappteam.com partially shares its mail servers with other domains; known examples include homechips.eu, maritimesafety.info and lebara.it.
Both relay1.netnames.net and relay2.netnames.net have a single IP address each — relay1.netnames.net resolves to 185.26.230.83 while relay2.netnames.net resolves to 185.26.230.89.