nalyzer.com - robtex.com
nalyzer.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=1785271837 | ||||||
Same first word
Similar names
DNS History
17 records (10 active, 7 former)
○NSns1.ipage.com2015-05-23 → 2017-10-07 · 4 obs
● 2017-10-07 14:13:06
○ 2026-07-28 21:13:20
○ 2026-07-28 21:13:22
●NSns1.name.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●NSns1djs.name.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
○NSns2.ipage.com2015-05-23 → 2017-10-07 · 4 obs
● 2017-10-07 14:13:06
○ 2026-07-28 21:13:20
○ 2026-07-28 21:13:22
●NSns2dqx.name.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●NSns3cfp.name.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●NSns4htz.name.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●MXalt1.aspmx.l.google.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●MXalt2.aspmx.l.google.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●MXalt3.aspmx.l.google.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●MXalt4.aspmx.l.google.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
●MXaspmx.l.google.com2026-07-28 → 2026-07-28 · 3 obs
● 2026-07-28 21:13:20
● 2026-07-28 21:13:22
○MXmx.nalyzer.com2015-05-23 → 2017-10-07 · 4 obs
● 2017-10-07 14:13:06
○ 2026-07-28 21:13:20
○ 2026-07-28 21:13:22
○A208.78.70.82015-05-23 → 2015-05-23 · 3 obs
○ 2017-10-07 14:13:06
○ 2026-07-28 21:13:22
○A66.96.147.1062016-12-05 → 2017-10-07 · 5 obs
● 2016-12-05 01:35:56
● 2017-10-07 14:13:06
○ 2026-07-28 21:13:20
○ 2026-07-28 21:13:22
○A66.96.147.1282015-05-23 → 2016-03-11 · 4 obs
● 2016-03-11 00:17:00
○ 2016-03-27 01:15:02
○ 2026-07-28 21:13:22
○A66.96.149.162016-03-27 → 2016-03-27 · 4 obs
● 2016-03-27 01:15:02
○ 2016-12-05 01:35:56
○ 2026-07-28 21:13:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net... | - |
| nalyzer.com | ns1djs.name.com, ns2dqx.name.com, ns3cfp.name.com, ns4htz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1djs.name.com, ns2dqx.name.com, ns3cfp.name.com, ns4htz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for nalyzer.com (unsigned zone)
⏱️ Timing
Total: 218ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1djs.name.com, ns2dqx.name.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=1DVAKQMwXzVc1-w |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1djs.name.com, ns1djs.name.com, ns2dqx.name.com...)
Analysis
Name Servers
nalyzer.com delegates to five name servers: ns1.name.com, ns1djs.name.com, ns2dqx.name.com and two others.
There is at least partial name server overlap between nalyzer.com and other domains — promogowild.com, evolutionholdings.com, verisage.us and two more among them.
These name servers regularly appear alongside ns4htz.name.com, ns3cfp.name.com, ns2kry.name.com and 7 other name servers in NS record sets.
Host names that have two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1djs.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2dqx.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3cfp.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4htz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1djs.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1djs.name.com resolve to 163.114.216.17 IP addresses each.
Mail Servers
Five mail servers handle nalyzer.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between nalyzer.com and other domains, including ns500731.ns500754.ns500671.ns500731.ns500754.ns500731.ns500731.ns500704.ns500704.ns500704.ns500704.ns500666.ns500666.ns500131.lustychickser.com, ns500698.ns500759.ns500759.ns500735.ns500698.ns500708.ns500686.ns500652.ns500652.ns500576.ns500619.ns500652.tracksymphony.com, ns500671.ns500742.ns500731.ns500671.ns500742.ns500754.ns500688.ns500678.ns500688.ns500688.ns500649.ns500671.ns500291.ns500291.ns500131.lustychickser.com and two others.
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.
Host names that have two IP addresses:
aspmx.l.google.com directs traffic to 172.253.139.26 and 2607:f8b0:4004:c23::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.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.