web64.com - dns.ninja
web64.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=1782302955 | ||||||
Subdomains
Same first word
Similar names
DNS History
12 records (8 active, 4 former)
●NSdina.ns.cloudflare.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
●NStom.ns.cloudflare.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
●MXalt1.aspmx.l.google.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
●MXalt2.aspmx.l.google.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
●MXaspmx.l.google.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
●MXaspmx2.googlemail.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
●MXaspmx3.googlemail.com2015-06-06 → 2026-06-24 · 2 obs
● 2026-06-24 12:29:22
○A104.28.30.572015-06-06 → 2018-08-29 · 4 obs
● 2018-08-29 00:14:52
○ 2026-03-24 07:26:46
○ 2026-06-24 12:29:22
○A104.28.31.572015-06-06 → 2018-08-29 · 4 obs
● 2018-08-29 00:14:52
○ 2026-03-24 07:26:46
○ 2026-06-24 12:29:22
○A2400:cb00:2048:1::681c:1e392016-12-03 → 2018-08-29 · 5 obs
● 2016-12-03 06:58:50
● 2018-08-29 00:14:52
○ 2026-03-24 07:26:46
○ 2026-06-24 12:29:22
○A2400:cb00:2048:1::681c:1f392016-12-03 → 2018-08-29 · 5 obs
● 2016-12-03 06:58:50
● 2018-08-29 00:14:52
○ 2026-03-24 07:26:46
○ 2026-06-24 12:29:22
●A94.23.0.512026-03-24 → 2026-06-24 · 3 obs
● 2026-03-24 07:26:46
● 2026-06-24 12:29:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| web64.com | dina.ns.cloudflare.com, tom.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.147
NS records: dina.ns.cloudflare.com, tom.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for web64.com (unsigned zone)
⏱️ Timing
Total: 194ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 94.23.0.51 |
| NS | 2 | dina.ns.cloudflare.com, tom.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 1 | v=spf1 a mx include:spf.mtasv.net ~all |
| SOA | 1 | dina.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (dina.ns.cloudflare.com, dina.ns.cloudflare.com, dina.ns.cloudflare.com...)
Analysis
Hierarchy
The parent domain of www.web64.com and cdn.web64.com is web64.com.
IP Addresses
web64.com directs to one IP number, which is 94.23.0.51.
Additional host names — including ns344081.ip-94-23-0.eu and www.web64.com — share IP numbers with web64.com.
Name Servers
web64.com uses two name servers for its delegation: dina.ns.cloudflare.com and tom.ns.cloudflare.com.
web64.com has the same name server delegation as a number of other domains, such as cwiki.us, finchvpn.my, hrlinq.com and two more.
web64.com has at least partial name server overlap with other domains, such as linsec.ca, notairesmontreal.pro, enbridgeincomefundholdings.ca and two others.
It is common to see these name servers used together with name servers kia.ns.cloudflare.com and dom.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
Hostname dina.ns.cloudflare.com directs to 108.162.192.107, 172.64.32.107 and 173.245.58.107 along with 3 other IP addresses.
Hostname tom.ns.cloudflare.com directs to 108.162.193.147, 172.64.33.147 and 173.245.59.147 along with 3 other IP addresses.
Mail Servers
web64.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
web64.com shares at least some of its mail servers with other domains — for example chase-insurance-agency.com, ns500734.ns500699.ns500734.ns500699.ns500734.ns500699.ns500693.ns500699.ns500693.ns500588.ns500588.ns500699.ns500588.dtrkdll.com, ns500759.ns500759.ns500698.ns500758.ns500735.ns500735.ns500735.ns500735.ns500698.ns500576.ns500576.ns500698.ns500698.ns500619.ns500619.trackreceptor.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
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 173.194.45.27 and 2607:f8b0:4004:c27::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::1a.
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 172.253.116.27 IP addresses each.