fighter.red - dns.ninja
fighter.red
red
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.red ⭐ | ||||||
| NS | a2.nic.red | ||||||
| NS | b0.nic.red | ||||||
| NS | c0.nic.red | ||||||
| SOA | a0.nic.redhostmaster@donuts.email serial=1781385131 | ||||||
Same first word
Similar names
DNS History
13 records (8 active, 5 former)
○NSdns10.hichina.com2016-12-10 → 2016-12-10 · 3 obs
○ 2017-08-08 04:06:44
○ 2026-06-13 21:28:58
○NSdns9.hichina.com2016-12-10 → 2016-12-10 · 3 obs
○ 2017-08-08 04:06:44
○ 2026-06-13 21:28:58
○NSexpirens3.hichina.com2017-08-08 → 2017-08-08 · 4 obs
● 2017-08-08 04:06:44
○ 2026-06-08 03:19:24
○ 2026-06-13 21:28:58
○NSexpirens4.hichina.com2017-08-08 → 2017-08-08 · 4 obs
● 2017-08-08 04:06:44
○ 2026-06-08 03:19:24
○ 2026-06-13 21:28:58
●NSns-cloud-e1.googledomains.com2026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●NSns-cloud-e2.googledomains.com2026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●NSns-cloud-e3.googledomains.com2026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●NSns-cloud-e4.googledomains.com2026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●A198.185.159.1442026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●A198.185.159.1452026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●A198.49.23.1442026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
●A198.49.23.1452026-06-08 → 2026-06-13 · 3 obs
● 2026-06-08 03:19:24
● 2026-06-13 21:28:58
○A47.89.58.1412017-08-08 → 2017-08-08 · 3 obs
○ 2026-06-08 03:19:24
○ 2026-06-13 21:28:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| red | a0.nic.red, a2.nic.red, b0.nic.red, c0.nic.red | 8 records |
| fighter.red | ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com | - |
✅ Authoritative Response
Server:216.239.34.110
NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fighter.red (unsigned zone)
⏱️ Timing
Total: 564ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.49.23.144, 198.185.159.144... |
| NS | 4 | ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com... |
| TXT | 1 | v=spf1 -all |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h2", |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (a0.nic.red, a0.nic.red, a2.nic.red...)
Analysis
IP Addresses
fighter.red points to four IP numbers: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
er-va.co.uk, blocstudio.co.uk, eastwoodlawstl.com plus two other host names have IP numbers in common with fighter.red.
Name Servers
fighter.red is delegated to four name servers, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
fighter.red has at least partial name server overlap with other domains, such as sleekis.com, flourishbound.com, thepuresalon.com and two others.
ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.