zaver.com - dns.ninja
zaver.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=1785839412 | ||||||
Subdomains
checkout.zaver.com |
Same first word
Similar names
DNS History
15 records (10 active, 5 former)
●NSns-1458.awsdns-54.org2026-02-17 → 2026-08-04 · 3 obs
● 2026-02-17 20:41:30
● 2026-08-04 10:35:16
●NSns-1643.awsdns-13.co.uk2026-02-17 → 2026-08-04 · 3 obs
● 2026-02-17 20:41:30
● 2026-08-04 10:35:16
●NSns-332.awsdns-41.com2026-02-17 → 2026-08-04 · 3 obs
● 2026-02-17 20:41:30
● 2026-08-04 10:35:16
●NSns-916.awsdns-50.net2026-02-17 → 2026-08-04 · 3 obs
● 2026-02-17 20:41:30
● 2026-08-04 10:35:16
○NSns73.domaincontrol.com2015-06-06 → 2017-09-02 · 4 obs
● 2017-09-02 10:25:40
○ 2026-02-17 20:41:30
○ 2026-08-04 10:35:16
○NSns74.domaincontrol.com2015-06-06 → 2017-09-02 · 4 obs
● 2017-09-02 10:25:40
○ 2026-02-17 20:41:30
○ 2026-08-04 10:35:16
●MXalt1.aspmx.l.google.com2026-02-17 → 2026-08-04 · 6 obs
● 2026-02-17 20:41:30
● 2026-06-16 10:51:36
○ 2026-06-18 23:05:50
● 2026-06-20 13:35:32
● 2026-08-04 10:35:16
●MXalt2.aspmx.l.google.com2026-02-17 → 2026-08-04 · 6 obs
● 2026-02-17 20:41:30
● 2026-06-16 10:51:36
○ 2026-06-18 23:05:50
● 2026-06-20 13:35:32
● 2026-08-04 10:35:16
●MXalt3.aspmx.l.google.com2026-02-17 → 2026-08-04 · 6 obs
● 2026-02-17 20:41:30
● 2026-06-16 10:51:36
○ 2026-06-18 23:05:50
● 2026-06-20 13:35:32
● 2026-08-04 10:35:16
●MXalt4.aspmx.l.google.com2026-02-17 → 2026-08-04 · 6 obs
● 2026-02-17 20:41:30
● 2026-06-16 10:51:36
○ 2026-06-18 23:05:50
● 2026-06-20 13:35:32
● 2026-08-04 10:35:16
●MXaspmx.l.google.com2026-02-17 → 2026-08-04 · 6 obs
● 2026-02-17 20:41:30
● 2026-06-16 10:51:36
○ 2026-06-18 23:05:50
● 2026-06-20 13:35:32
● 2026-08-04 10:35:16
○MXmailstore1.secureserver.net2015-06-06 → 2017-09-02 · 4 obs
● 2017-09-02 10:25:40
○ 2026-02-17 20:41:30
○ 2026-08-04 10:35:16
○MXsmtp.secureserver.net2015-06-06 → 2017-09-02 · 4 obs
● 2017-09-02 10:25:40
○ 2026-02-17 20:41:30
○ 2026-08-04 10:35:16
●A198.202.211.12026-02-17 → 2026-08-04 · 6 obs
● 2026-02-17 20:41:30
● 2026-06-16 10:51:36
○ 2026-06-18 23:05:50
● 2026-06-20 13:35:32
● 2026-08-04 10:35:16
○A50.63.202.632015-06-06 → 2017-09-02 · 4 obs
● 2017-09-02 10:25:40
○ 2026-02-17 20:41:30
○ 2026-08-04 10:35:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net... | - |
| zaver.com | ns-332.awsdns-41.com, ns-916.awsdns-50.net, ns-1643.awsdns-13.co.uk, ns-1458.awsdns-54.org | 2 records |
✅ Authoritative Response
Server:205.251.193.76
NS records: ns-332.awsdns-41.com, ns-916.awsdns-50.net, ns-1643.awsdns-13.co.uk, ns-1458.awsdns-54.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for zaver.com (unsigned zone)
⏱️ Timing
Total: 311ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.202.211.1 |
| NS | 4 | ns-1458.awsdns-54.org, ns-1643.awsdns-13.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 4 | apple-domain-verification=QUCrO2KLqxE5Cn, google-site-verification=uHsu7_y-iaRTvIx... |
| SOA | 1 | ns-332.awsdns-41.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-332.awsdns-41.com, ns-332.awsdns-41.com)
Analysis
Hierarchy
checkout.zaver.com is delegated beneath zaver.com.
IP Addresses
zaver.com has exactly one IP address — 198.202.211.1.
vkontextu.com, playerprofit.com, ryptic.com plus two other host names have IP numbers in common with zaver.com.
Name Servers
Four name servers handle the delegation for zaver.com: ns-332.awsdns-41.com, ns-916.awsdns-50.net, ns-1458.awsdns-54.org and ns-1643.awsdns-13.co.uk.
There is at least partial name server overlap between zaver.com and other domains — cpelink.com, bayareasyntheticgrass.com, payermax-akm.com and two more among them.
All four hostnames — ns-332.awsdns-41.com, ns-916.awsdns-50.net, ns-1458.awsdns-54.org and ns-1643.awsdns-13.co.uk — resolve to two IP numbers apiece: ns-332.awsdns-41.com to 205.251.193.76 and 2600:9000:5301:4c00::1; ns-916.awsdns-50.net to 205.251.195.148 and 2600:9000:5303:9400::1; ns-1458.awsdns-54.org to 205.251.197.178 and 2600:9000:5305:b200::1; ns-1643.awsdns-13.co.uk to 205.251.198.107 and 2600:9000:5306:6b00::1.
Mail Servers
Five mail servers handle zaver.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by zaver.com are shared with other domains: nahlleague.wpengine.com, papercitymag.com, glenbrookcreations.com and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 173.194.45.26 and 2607:f8b0:4004:c23::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::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.