hap.tc - dns.ninja
hap.tc
tc
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | roots.nic.tc ⭐ | ||||||
| NS | root1.zone.tc | ||||||
| NS | root2.zone.tc | ||||||
| NS | root3.zone.tc | ||||||
| NS | root4.zone.tc | ||||||
| NS | root5.zone.tc | ||||||
| NS | root6.zone.tc | ||||||
| NS | root7.zone.tc | ||||||
| NS | root8.zone.tc | ||||||
| TXT | Generation Time: 1784495391 | ||||||
| SOA | roots.nic.tczone@tc serial=2026075011 | ||||||
Same first word
Similar names
DNS History
10 records (10 active, 0 former)
●NSns1-03.azure-dns.com2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●NSns2-03.azure-dns.net2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●NSns3-03.azure-dns.org2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●NSns4-03.azure-dns.info2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●MXalt1.aspmx.l.google.com2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●MXalt2.aspmx.l.google.com2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●MXaspmx.l.google.com2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●MXaspmx2.googlemail.com2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●MXaspmx3.googlemail.com2026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
●A137.135.107.942026-02-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:22:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| tc | root4.zone.tc, root5.zone.tc, root1.zone.tc, root2.zone.tc... | 12 records |
| hap.tc | ns4-03.azure-dns.info, ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org | - |
✅ Authoritative Response
Server:204.14.183.3
NS records: ns4-03.azure-dns.info, ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hap.tc (unsigned zone)
⏱️ Timing
Total: 592ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 137.135.107.94 |
| NS | 4 | ns1-03.azure-dns.com, ns2-03.azure-dns.net... |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 1 | MS=ms78812504 |
| SOA | 1 | ns1-03.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (root1.zone.tc, root2.zone.tc, root3.zone.tc...)
Analysis
IP Addresses
hap.tc resolves to one IP address: 137.135.107.94.
Name Servers
The authoritative name servers for hap.tc are ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.
At least some of hap.tc's name servers are shared with other domains, for example moe.edu.ps, msa-msn-uat.net, vsic.com and two more.
Four hostnames, each resolving to a pair of IP addresses: ns1-03.azure-dns.com directs to 13.107.236.3 and 2603:1061:0:700::3; ns4-03.azure-dns.info directs to 208.84.5.3 and 2620:1ec:bda:700::3; ns2-03.azure-dns.net directs to 150.171.21.3 and 2620:1ec:8ec:700::3; ns3-03.azure-dns.org directs to 204.14.183.3 and 2a01:111:4000:700::3.
Mail Servers
hap.tc has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
hap.tc has at least partial mail server overlap with other domains such as softpol3.webd.pl, ns500841.ns500821.ns500841.ns500794.ns500841.ns500795.ns500794.ns500821.ns500794.ns500821.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, sheldonrev.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 172.253.63.26 and 2607:f8b0:4004:c1d::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.