zacpp.com - dns.ninja
zacpp.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=1786215684 | ||||||
Same first word
zacpp.com |
Similar names
DNS History
11 records (9 active, 2 former)
●NSns3.hover.com2026-02-15 → 2026-08-08 · 3 obs
● 2026-02-15 13:03:08
● 2026-08-08 19:27:08
●MXalt1.aspmx.l.google.com2018-01-08 → 2026-08-08 · 3 obs
● 2018-01-08 09:58:24
● 2026-08-08 19:27:08
●MXalt2.aspmx.l.google.com2018-01-08 → 2026-08-08 · 3 obs
● 2018-01-08 09:58:24
● 2026-08-08 19:27:08
●MXaspmx.l.google.com2018-01-08 → 2026-08-08 · 3 obs
● 2018-01-08 09:58:24
● 2026-08-08 19:27:08
●MXaspmx2.googlemail.com2018-01-08 → 2026-08-08 · 3 obs
● 2018-01-08 09:58:24
● 2026-08-08 19:27:08
●MXaspmx3.googlemail.com2018-01-08 → 2026-08-08 · 3 obs
● 2018-01-08 09:58:24
● 2026-08-08 19:27:08
○MXmx.hover.com.cust.hostedemail.com2016-12-19 → 2016-12-19 · 3 obs
○ 2018-01-08 09:58:24
○ 2026-08-08 19:27:08
●A162.243.148.602018-01-08 → 2026-08-08 · 3 obs
● 2018-01-08 09:58:24
● 2026-08-08 19:27:08
○A64.98.145.302016-12-19 → 2016-12-19 · 3 obs
○ 2018-01-08 09:58:24
○ 2026-08-08 19:27:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| zacpp.com | ns3.hover.com, ns1.hover.com, ns2.hover.com | 6 records |
✅ Authoritative Response
Server:64.99.96.33
NS records: ns3.hover.com, ns1.hover.com, ns2.hover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for zacpp.com (unsigned zone)
⏱️ Timing
Total: 219ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.243.148.60 |
| NS | 2 | ns2.hover.com, ns1.hover.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns1.hover.com dnsmaster.hover.com |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns3.hover.com, ns3.hover.com, ns1.hover.com...)
Analysis
IP Addresses
zacpp.com points to a single IP number: 162.243.148.60.
Host names such as kendallgifford.com, hikespy.com and jedis.com share their IP numbers with zacpp.com.
Name Servers
The authoritative name servers for zacpp.com are ns1.hover.com, ns2.hover.com and ns3.hover.com — three in total.
There is at least partial name server overlap between zacpp.com and other domains — teed.ca, phillyconnect.net, oxforddigitalmarketing.com and two more among them.
These name servers are routinely deployed together with the name servers ns4.hover.com.
ns1.hover.com, ns2.hover.com and ns3.hover.com all resolve to exactly two IP numbers apiece: ns1.hover.com → 216.40.47.26 and 2604:4000:0:d:216:40:47:26; ns2.hover.com → 64.98.148.13 and 2604:4000:2800:d:64:99:148:13; ns3.hover.com → 64.99.96.33 and 2604:4000:0:d:64:99:96:33.
Mail Servers
Five mail servers handle zacpp.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
zacpp.com shares mail servers — at least in part — with other domains, including orientasian.in, ns500736.ns500736.ns500698.ns500736.ns500735.ns500736.ns500708.ns500708.ns500708.ns500619.ns500576.ns500619.ns500619.trackreceptor.com, ns500671.ns500754.ns500671.ns500704.ns500688.ns500704.ns500705.lusty(0x736c7574)z.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 64.233.180.27 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.