zapyard.com - robtex.com
zapyard.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 173.254.1.134🇺🇸 EIGI | ||||||
| PTR | 173-254-1-134.unifiedlayer.com | ||||||
| NS | ns1.bluehost.com ⭐ | ||||||
| A | 162.159.24.80 Cloudflare | ||||||
| PTR | ns1.bluehost.com | ||||||
| NS | ns2.bluehost.com | ||||||
| A | 162.159.25.175 Cloudflare | ||||||
| PTR | ns2.bluehost.com | ||||||
| MX | mail.zapyard.com ⭐ | ||||||
| A | 173.254.1.134🇺🇸 EIGI | ||||||
| PTR | 173-254-1-134.unifiedlayer.com | ||||||
| MX | ms20021372.msv1.invalid(32767) 🔒 | ||||||
| TXT | v=spf1 include:spf.protection.outlook.com -all | ||||||
| TXT | MS=ms20021372 | ||||||
| TXT | v=spf1 a mx include:websitewelcome.com ~all | ||||||
| TXT | google-site-verification=YICaEiJCwQd0Mt94WlgQutSrh5hJCuzo4Kwo9nZUCM4 | ||||||
| SOA | ns1.bluehost.comroot@box2487.bluehost.com 2026-02-03 #0 | ||||||
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=1771291435 | ||||||
Similar names
paradyz.pl |
payzard.com |
paradyz.ru |
paradyz.de |
parazyd.org |
paradyz.com |
paradyz.md |
paradyz.sk |
paradyz.com.pl |
paradyz.eu |
paradyz.ir |
DNS History
5 records (5 active, 0 former)
●NSns1.bluehost.com2026-02-21 → 2026-02-21 · 2 obs
● 2026-02-21 04:38:04
●NSns2.bluehost.com2026-02-21 → 2026-02-21 · 2 obs
● 2026-02-21 04:38:04
●MXmail.zapyard.com2026-02-21 → 2026-02-21 · 2 obs
● 2026-02-21 04:38:04
●MXms20021372.msv1.invalid2026-02-21 → 2026-02-21 · 2 obs
● 2026-02-21 04:38:04
●A173.254.1.1342026-02-21 → 2026-02-21 · 2 obs
● 2026-02-21 04:38:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| zapyard.com | ns1.bluehost.com, ns2.bluehost.com | - |
✅ Authoritative Response
Server: 162.159.25.175
NS records: ns1.bluehost.com, ns2.bluehost.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for zapyard.com (unsigned zone)
⏱️ Timing
Total: 401ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 173.254.1.134 |
| NS | 2 | ns2.bluehost.com, ns1.bluehost.com |
| MX | 2 | ms20021372.msv1.invalid (pri: 32767), mail.zapyard.com (pri: 0) |
| TXT | 4 | MS=ms20021372, v=spf1 a mx include:websitewelcome.com ~... |
| SOA | 1 | ns1.bluehost.com root.box2487.bluehost.c |
AI analysis
zapyard.com points to an IP address: 173.254.1.134.
Other host names, such as 173-254-1-134.unifiedlayer.com, mail.sapyard.com and sapyard.com, share IP numbers with zapyard.com.
Two name servers ns1.bluehost.com and ns2.bluehost.com handle the delegation for zapyard.com.
zapyard.com shares the same name server setup as other domains, for instance wessextowers.com, amaana.org, 3wm.us, joshuatreetourism.com and mciverlab.com.
zapyard.com at least partially shares name servers with other domains, including unitedfsi.com and telebirads.com.
Host names with one IP:
ns1.bluehost.com points to: 162.159.24.80
ns2.bluehost.com points to: 162.159.25.175
zapyard.com is handled by two mail servers: mail.zapyard.com and ms20021372.msv1.invalid.
Host names with a single IP address: mail.zapyard.com points to 173.254.1.134.