combatflags.com - dns.ninja
combatflags.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=1783295281 | ||||||
Previously MX for
combatflags.com |
Subdomains
www.combatflags.com |
Same first word
combatflags.com |
DNS History
15 records (8 active, 7 former)
○NSns1.giantserver.net2016-11-25 → 2016-11-25 · 4 obs
● 2016-11-25 02:26:08
○ 2017-10-18 22:13:52
○ 2026-07-05 23:48:26
○NSns1.irpisnet.com2008-03-09 → 2008-03-09 · 3 obs
○ 2015-10-27 17:26:38
○ 2026-07-05 23:48:26
○NSns2.giantserver.net2016-11-25 → 2016-11-25 · 4 obs
● 2016-11-25 02:26:08
○ 2017-10-18 22:13:52
○ 2026-07-05 23:48:26
○NSns2.irpisnet.com2008-03-09 → 2008-03-09 · 3 obs
○ 2015-10-27 17:26:38
○ 2026-07-05 23:48:26
●NSns65.domaincontrol.com2017-10-18 → 2026-07-05 · 3 obs
● 2017-10-18 22:13:52
● 2026-07-05 23:48:26
●NSns66.domaincontrol.com2017-10-18 → 2026-07-05 · 3 obs
● 2017-10-18 22:13:52
● 2026-07-05 23:48:26
●MXalt1.aspmx.l.google.com2016-11-25 → 2026-07-05 · 3 obs
● 2016-11-25 02:26:08
● 2026-07-05 23:48:26
●MXalt2.aspmx.l.google.com2016-11-25 → 2026-07-05 · 3 obs
● 2016-11-25 02:26:08
● 2026-07-05 23:48:26
●MXalt3.aspmx.l.google.com2016-11-25 → 2026-07-05 · 3 obs
● 2016-11-25 02:26:08
● 2026-07-05 23:48:26
●MXalt4.aspmx.l.google.com2016-11-25 → 2026-07-05 · 3 obs
● 2016-11-25 02:26:08
● 2026-07-05 23:48:26
●MXaspmx.l.google.com2016-11-25 → 2026-07-05 · 3 obs
● 2016-11-25 02:26:08
● 2026-07-05 23:48:26
○MXcombatflags.com2008-03-09 → 2008-03-09 · 3 obs
○ 2015-10-27 17:26:38
○ 2026-07-05 23:48:26
○A209.59.163.72016-11-25 → 2016-11-25 · 4 obs
● 2016-11-25 02:26:08
○ 2017-10-18 22:13:52
○ 2026-07-05 23:48:26
●A23.227.38.322017-10-18 → 2026-07-05 · 3 obs
● 2017-10-18 22:13:52
● 2026-07-05 23:48:26
○A72.52.243.1942008-03-09 → 2008-03-09 · 3 obs
○ 2015-10-27 17:26:38
○ 2026-07-05 23:48:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| combatflags.com | ns66.domaincontrol.com, ns65.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.102.43
NS records: ns66.domaincontrol.com, ns65.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for combatflags.com (unsigned zone)
⏱️ Timing
Total: 813ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.32 |
| NS | 2 | ns66.domaincontrol.com, ns65.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | facebook-domain-verification=y0wen5z6gar, v=spf1 include:servers.mcsv.net ?all |
| SOA | 1 | ns65.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns66.domaincontrol.com, ns66.domaincontrol.com, ns65.domaincontrol.com...)
Analysis
Hierarchy
combatflags.com is the parent zone for www.combatflags.com.
IP Addresses
combatflags.com resolves to just one IP address, 23.227.38.32.
Two other host names, along with tbfbags.com, www.rhinousainc.com and spatchskin.com, also share IP numbers with combatflags.com.
Name Servers
combatflags.com is served by two delegated name servers, ns65.domaincontrol.com and ns66.domaincontrol.com.
combatflags.com shares its NS records with other domains, for example birdiechance.co.uk, allynwood.org, sana.engineering and two others.
The DNS delegation for combatflags.com at least partly coincides with that of other domains, axonsolutions.co being one example.
Each of the two host names carries two IP addresses: ns65.domaincontrol.com points to 97.74.102.43 and 2603:5:2164::2b, and ns66.domaincontrol.com points to 173.201.70.43 and 2603:5:2264::2b.
Mail Servers
Mail for combatflags.com is handled by five mail servers, namely 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 combatflags.com and other domains, including ns500731.ns500731.ns500742.ns500754.ns500742.ns500731.ns500731.ns500705.ns500688.ns500671.ns500688.ns500671.ns500291.ns500153.tenderladiesbz.com, ns500759.ns500698.ns500759.ns500759.ns500759.ns500758.ns500736.ns500736.ns500735.ns500735.ns500735.ns500735.ns500698.ns500708.ns500698.ns500698.trackreceptor.com, tolublaw.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com maps to two IP addresses — 172.253.62.27 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.26 and 2a00:1450:400c:c23::1a.