ngvanguard.com - robtex.com
ngvanguard.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=1774536957 | ||||||
Previously NS for
ngvanguard.com |
Same first word
ngvanguard.com |
DNS History
12 records (8 active, 4 former)
○NSngvanguard.com2018-11-28 → 2018-11-28 · 3 obs
○ 2026-02-22 19:29:36
○ 2026-03-26 15:19:58
●NSns1.bluehost.com2026-02-22 → 2026-03-26 · 3 obs
● 2026-02-22 19:29:36
● 2026-03-26 15:19:58
○NSns1.ngvanguard.com2018-11-28 → 2018-11-28 · 3 obs
○ 2026-02-22 19:29:36
○ 2026-03-26 15:19:58
●NSns2.bluehost.com2026-02-22 → 2026-03-26 · 3 obs
● 2026-02-22 19:29:36
● 2026-03-26 15:19:58
○NSns2.ngvanguard.com2018-11-28 → 2018-11-28 · 3 obs
○ 2026-02-22 19:29:36
○ 2026-03-26 15:19:58
●MXalt1.aspmx.l.google.com2026-02-22 → 2026-03-26 · 2 obs
● 2026-03-26 15:19:58
●MXalt2.aspmx.l.google.com2026-02-22 → 2026-03-26 · 2 obs
● 2026-03-26 15:19:58
●MXalt3.aspmx.l.google.com2026-02-22 → 2026-03-26 · 2 obs
● 2026-03-26 15:19:58
●MXalt4.aspmx.l.google.com2026-02-22 → 2026-03-26 · 2 obs
● 2026-03-26 15:19:58
●MXaspmx.l.google.com2026-02-22 → 2026-03-26 · 2 obs
● 2026-03-26 15:19:58
●A50.87.253.232026-02-22 → 2026-03-26 · 3 obs
● 2026-02-22 19:29:36
● 2026-03-26 15:19:58
○A67.55.121.972018-11-28 → 2018-11-28 · 3 obs
○ 2026-02-22 19:29:36
○ 2026-03-26 15:19:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ngvanguard.com | ns1.bluehost.com, ns2.bluehost.com | 2 records |
✅ Authoritative Response
Server:162.159.25.175
NS records: ns1.bluehost.com, ns2.bluehost.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ngvanguard.com (unsigned zone)
⏱️ Timing
Total: 264ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 50.87.253.23 |
| NS | 2 | ns1.bluehost.com, ns2.bluehost.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 a mx include:websitewelcome.com ~, google-site-verification=ZRYlTAPpeFHdg5j |
| SOA | 1 | ns1.bluehost.com root.box2152.bluehost.c |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)
Analysis
IP Addresses
ngvanguard.com resolves to one IP number: 50.87.253.23.
other host names including jkdesign4me.com, reliancefp.com, exetergroup.net, ermutek.com and mail.jennyeldredge.com share IP numbers with ngvanguard.com.
Name Servers
ngvanguard.com is delegated to two name servers ns1.bluehost.com and ns2.bluehost.com.
ngvanguard.com shares the same name server setup as other domains, for instance yjz.vcj.mybluehost.me, nicole-jackson.com, offgridandy.com, spiralpathdesigns.com and clessence.com.
ngvanguard.com shares name servers with other domains at least partially, for example everydayafs.com and rain.studio.
Host names with one IP number:
ns1.bluehost.com points to 162.159.24.80
ns2.bluehost.com points to 162.159.25.175
Mail Servers
ngvanguard.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
ngvanguard.com shares some mail servers with other domains, at least partially, for instance ns500821.ns500821.ns500841.ns500794.ns500795.ns500794.ns500821.ns500794.ns500821.ns500795.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500765.ns500699.ns500693.ns500693.ns500734.ns500693.ns500734.ns500699.ns500699.ns500588.ns500693.ns500632.ns500632.ns500588.ns500578.ns500110.dtrkdll.com, ns500734.ns500699.ns500693.ns500693.ns500693.ns500699.ns500734.ns500699.ns500699.ns500588.ns500588.ns500588.ns500588.ns500683.ns500588.ns500683.ns500602.dtrkdll.com, ns500698.ns500759.ns500759.ns500698.ns500698.ns500698.ns500698.ns500698.ns500698.ns500708.ns500698.ns500708.ns500576.ns500619.ns500576.ns500576.ns500652.trackreceptor.com and ns500742.ns500742.ns500754.ns500742.ns500731.ns500704.ns500731.ns500649.ns500688.ns500649.ns500688.ns500291.ns500153.tenderladiesbz.com.
these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c25::1b and 142.251.167.27
alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1b and 192.178.128.27
alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1b and 172.253.135.26
alt3.aspmx.l.google.com points to 2a00:1450:4001:c21::1a and 142.251.127.26
alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1a and 173.194.76.26