badflag.com - dns.ninja
badflag.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=1786834239 | ||||||
Same first word
badflag.com |
DNS History
12 records (8 active, 4 former)
●NSns67.domaincontrol.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
●NSns68.domaincontrol.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
●MXalt1.aspmx.l.google.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
●MXalt2.aspmx.l.google.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
●MXaspmx.l.google.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
●MXaspmx2.googlemail.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
●MXaspmx3.googlemail.com2017-02-16 → 2026-08-15 · 2 obs
● 2026-08-15 23:04:24
○A198.185.159.1442017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-08-15 23:04:24
○A198.185.159.1452017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-08-15 23:04:24
○A198.49.23.1442017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-08-15 23:04:24
○A198.49.23.1452017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-08-15 23:04:24
●A23.227.38.322026-04-09 → 2026-08-15 · 3 obs
● 2026-04-09 16:13:28
● 2026-08-15 23:04:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net... | - |
| badflag.com | ns67.domaincontrol.com, ns68.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.103.44
NS records: ns67.domaincontrol.com, ns68.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for badflag.com (unsigned zone)
⏱️ Timing
Total: 819ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.32 |
| NS | 2 | ns67.domaincontrol.com, ns68.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | klaviyo-site-verification=TBwcXh, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns67.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns67.domaincontrol.com, ns67.domaincontrol.com, ns68.domaincontrol.com...)
Analysis
IP Addresses
badflag.com points to a single IP number: 23.227.38.32.
Additional host names — casamaine.com.mx, stitchedmodern.com, kraftweddingpapers.com and two others — share IP numbers with badflag.com.
Name Servers
Two name servers handle the delegation for badflag.com: ns67.domaincontrol.com and ns68.domaincontrol.com.
badflag.com shares its name server setup with other domains, including turbine-studio.com, lawbooksinc.com, tomswords.com and two others.
badflag.com is at least partially co-delegated on name servers with other domains, such as itneti.com.
ns67.domaincontrol.com and ns68.domaincontrol.com both carry two IP addresses. The A records for ns67.domaincontrol.com are 97.74.103.44 and 2603:5:2174::2c; the A records for ns68.domaincontrol.com are 173.201.71.44 and 2603:5:2274::2c.
Mail Servers
Five mail servers handle badflag.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
badflag.com shares mail servers — at least in part — with other domains, including fayettesch.org, jovonnafallongettingdinnerdone.com, ns500765.ns500734.ns500699.ns500693.ns500699.ns500693.ns500588.ns500588.ns500699.ns500699.ns500588.ns500683.ns500602.dtrkdll.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to two addresses: 142.251.163.26 and 2607:f8b0:4004:c19::1a.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c14::1a IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.26 IP addresses.