techpi.com - dns.ninja
techpi.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=1785701867 | ||||||
Previously MX for
techpi.com |
Same first word
techpi.com |
Similar names
DNS History
21 records (8 active, 13 former)
●NSdns1.p01.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns1.p09.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns2.p02.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns2.p09.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns3.p03.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns3.p09.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns4.p04.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
●NSdns4.p09.nsone.net2026-02-15 → 2026-08-02 · 3 obs
● 2026-02-15 20:51:52
● 2026-08-02 20:19:30
○NSlocalhost2016-12-05 → 2016-12-05 · 4 obs
● 2016-12-05 09:01:02
○ 2017-08-30 13:09:30
○ 2026-08-02 20:19:30
○NSmaster.dns.ne.jp2015-06-13 → 2016-02-09 · 4 obs
● 2016-02-09 10:43:56
○ 2016-04-26 03:56:00
○ 2026-08-02 20:19:30
○NSns1.dns.ne.jp2015-06-13 → 2016-02-09 · 4 obs
● 2016-02-09 10:43:56
○ 2016-04-26 03:56:00
○ 2026-08-02 20:19:30
○NSns1.mytrafficmanagement.com2016-12-05 → 2016-12-05 · 4 obs
● 2016-12-05 09:01:02
○ 2017-08-30 13:09:30
○ 2026-08-02 20:19:30
○NSns1637.ztomy.com2017-08-30 → 2017-08-30 · 4 obs
● 2017-08-30 13:09:30
○ 2026-02-15 20:51:52
○ 2026-08-02 20:19:30
○NSns2.dns.ne.jp2015-06-13 → 2016-02-09 · 4 obs
● 2016-02-09 10:43:56
○ 2016-04-26 03:56:00
○ 2026-08-02 20:19:30
○NSns2.mytrafficmanagement.com2016-12-05 → 2016-12-05 · 4 obs
● 2016-12-05 09:01:02
○ 2017-08-30 13:09:30
○ 2026-08-02 20:19:30
○NSns2637.ztomy.com2017-08-30 → 2017-08-30 · 4 obs
● 2017-08-30 13:09:30
○ 2026-02-15 20:51:52
○ 2026-08-02 20:19:30
○MXtechpi.com2015-06-13 → 2016-02-09 · 4 obs
● 2016-02-09 10:43:56
○ 2016-04-26 03:56:00
○ 2026-08-02 20:19:30
○A104.130.124.962016-12-05 → 2016-12-05 · 4 obs
● 2016-12-05 09:01:02
○ 2017-08-30 13:09:30
○ 2026-08-02 20:19:30
○A204.11.56.372017-08-30 → 2026-02-15 · 5 obs
● 2017-08-30 13:09:30
● 2026-02-15 20:51:52
○ 2026-02-18 17:44:34
○ 2026-08-02 20:19:30
○A59.106.13.332015-06-13 → 2016-02-09 · 4 obs
● 2016-02-09 10:43:56
○ 2016-04-26 03:56:00
○ 2026-08-02 20:19:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net... | - |
| techpi.com | dns1.p01.nsone.net, dns2.p02.nsone.net, dns3.p03.nsone.net, dns4.p04.nsone.net | - |
✅ Authoritative Response
Server:198.51.44.1
NS records: dns1.p01.nsone.net, dns2.p02.nsone.net, dns3.p03.nsone.net, dns4.p04.nsone.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for techpi.com (unsigned zone)
⏱️ Timing
Total: 477ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | dns1.p09.nsone.net, dns2.p09.nsone.net... |
| SOA | 1 | dns1.p09.nsone.net parked.nsone.net |
Analysis
Name Servers
techpi.com has 8 name servers — dns1.p01.nsone.net, dns2.p02.nsone.net, dns3.p03.nsone.net and 5 others.
techpi.com shares at least some of its name servers with other domains, including cobactan.it, newwordswithfriends.it, union-news.com and two others.
These name servers are frequently seen alongside dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net and 7 other name servers.
Hosts with two IP numbers each:
dns1.p01.nsone.net resolves to 198.51.44.1 and 2620:4d:4000:6259:7:1:0:1.
dns2.p02.nsone.net resolves to 198.51.45.2 and 2a00:edc0:6259:7:2::2.
dns3.p03.nsone.net resolves to 198.51.44.67 and 2620:4d:4000:6259:7:3:0:3.
dns4.p04.nsone.net resolves to 198.51.45.68 and 2a00:edc0:6259:7:4::4.
dns1.p09.nsone.net resolves to 198.51.44.9 and 2620:4d:4000:6259:7:9:0:1.
dns2.p09.nsone.net resolves to 198.51.45.9 and 2a00:edc0:6259:7:9::2.
dns3.p09.nsone.net resolves to 198.51.44.73 and 2620:4d:4000:6259:7:9:0:3.
dns4.p09.nsone.net resolves to 198.51.45.73 and 2a00:edc0:6259:7:9::4.