fighterzone.com - dns.ninja
fighterzone.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=1783239646 | ||||||
Same first word
fighterzone.biz |
fighterzone.com |
fighterzone.mobi |
fighterzone.co |
fighterzone.info |
fighterzone.de |
fighterzone.tv |
Similar names
enzofreight.com |
freezinghot.com |
freightzone.net |
freezinghot.ca |
freightzone.co.zw |
freightzone.com |
freightzone.eu |
zenithforge.com |
DNS History
15 records (8 active, 7 former)
○NSns1.mediatemple.net2016-02-02 → 2018-09-13 · 5 obs
● 2016-02-02 06:17:38
● 2018-09-13 14:47:48
○ 2026-02-27 18:40:50
○ 2026-07-05 08:34:54
○NSns2.mediatemple.net2016-02-02 → 2018-09-13 · 5 obs
● 2016-02-02 06:17:38
● 2018-09-13 14:47:48
○ 2026-02-27 18:40:50
○ 2026-07-05 08:34:54
●NSns35.domaincontrol.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
●NSns36.domaincontrol.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
○NSns43.corecommerce.com2015-07-12 → 2015-11-14 · 4 obs
● 2015-11-14 09:24:12
○ 2016-02-02 06:17:38
○ 2026-07-05 08:34:54
○NSns44.corecommerce.com2015-07-12 → 2015-11-14 · 4 obs
● 2015-11-14 09:24:12
○ 2016-02-02 06:17:38
○ 2026-07-05 08:34:54
●MXalt1.aspmx.l.google.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
●MXalt2.aspmx.l.google.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
●MXalt3.aspmx.l.google.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
●MXalt4.aspmx.l.google.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
●MXaspmx.l.google.com2026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
○MXmail.fighterzone.com2016-02-02 → 2018-09-13 · 4 obs
● 2018-09-13 14:47:48
○ 2026-02-27 18:40:50
○ 2026-07-05 08:34:54
●A151.101.2.1592026-02-27 → 2026-07-05 · 3 obs
● 2026-02-27 18:40:50
● 2026-07-05 08:34:54
○A67.192.197.1032015-07-12 → 2015-11-14 · 4 obs
● 2015-11-14 09:24:12
○ 2016-02-02 06:17:38
○ 2026-07-05 08:34:54
○A72.47.224.852016-02-02 → 2018-09-13 · 5 obs
● 2016-02-02 06:17:38
● 2018-09-13 14:47:48
○ 2026-02-27 18:40:50
○ 2026-07-05 08:34:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| fighterzone.com | ns35.domaincontrol.com, ns36.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.75.18
NS records: ns35.domaincontrol.com, ns36.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fighterzone.com (unsigned zone)
⏱️ Timing
Total: 179ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 151.101.2.159 |
| NS | 2 | ns35.domaincontrol.com, ns36.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns35.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)
Analysis
IP Addresses
fighterzone.com resolves to one IP address: 151.101.2.159.
mail.trinityconnection.com, htkarchitects.com, stadtkueche.de and two other host names share IP numbers with fighterzone.com.
Name Servers
The NS records for fighterzone.com delegate to ns35.domaincontrol.com and ns36.domaincontrol.com.
fighterzone.com uses the same name servers as several other domains — among them hxem.com, beercansailor.com, gamedroidlabs.com and two more.
ns35.domaincontrol.com resolves to 97.74.107.18 and 2603:5:21b1::12. Likewise, ns36.domaincontrol.com resolves to 173.201.75.18 and 2603:5:22b1::12 — two IP addresses apiece.
Mail Servers
fighterzone.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
fighterzone.com has at least partial mail server overlap with other domains such as ns500698.ns500698.ns500758.ns500759.ns500698.ns500698.ns500735.ns500735.ns500698.ns500736.ns500708.ns500708.ns500652.ns500619.ns500619.trackreceptor.com, ns500699.ns500699.ns500699.ns500693.ns500693.ns500693.ns500699.ns500588.ns500588.ns500588.ns500699.ns500693.ns500588.ns500110.dtrkdll.com, ns500734.ns500693.ns500693.ns500699.ns500734.ns500588.ns500588.ns500588.ns500683.ns500588.ns500632.ns500612.ns500588.ns500632.ns500612.ns500578.ns500110.dtrkdll.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
The A records for aspmx.l.google.com return 142.251.167.26 and 2607:f8b0:4004:c1d::1b.
The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1a.
The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1b.
The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1a.
The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1b.