badflag.com - robtex.com
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=1777528421 | ||||||
Same first word
badflag.com |
DNS History
12 records (8 active, 4 former)
●NSns67.domaincontrol.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
●NSns68.domaincontrol.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
●MXalt1.aspmx.l.google.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
●MXalt2.aspmx.l.google.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
●MXaspmx.l.google.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
●MXaspmx2.googlemail.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
●MXaspmx3.googlemail.com2017-02-16 → 2026-04-30 · 2 obs
● 2026-04-30 05:54:56
○A198.185.159.1442017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-04-30 05:54:56
○A198.185.159.1452017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-04-30 05:54:56
○A198.49.23.1442017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-04-30 05:54:56
○A198.49.23.1452017-02-16 → 2020-01-01 · 4 obs
● 2020-01-01 06:11:14
○ 2026-04-09 16:13:28
○ 2026-04-30 05:54:56
●A23.227.38.322026-04-09 → 2026-04-30 · 3 obs
● 2026-04-09 16:13:28
● 2026-04-30 05:54:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net... | - |
| badflag.com | ns67.domaincontrol.com, ns68.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.71.44
NS records: ns67.domaincontrol.com, ns68.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for badflag.com (unsigned zone)
⏱️ Timing
Total: 249ms | 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 an IP address: 23.227.38.32.
other host names include stitchedmodern.com, kraftweddingpapers.com, forunaturally.com, venuedu.com and halfmoon.biz; they share IP numbers with badflag.com.
Name Servers
Two name servers ns67.domaincontrol.com and ns68.domaincontrol.com handle the delegation for badflag.com.
badflag.com shares the same name server setup as other domains, for instance turbine-studio.com, lawbooksinc.com, leadgeneration360.com, tomswords.com and carlyle.tv.
badflag.com shares name servers with other domains at least partially, for example itneti.com.
Host names with two IP numbers:
ns67.domaincontrol.com points to 2603:5:2174::2c and 97.74.103.44.
ns68.domaincontrol.com points to 2603:5:2274::2c and 173.201.71.44.
Mail Servers
badflag.com is served by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
badflag.com shares at least partially some mail servers with other domains, for instance fayettesch.org, ns500765.ns500734.ns500699.ns500693.ns500699.ns500693.ns500588.ns500588.ns500699.ns500699.ns500588.ns500683.ns500602.dtrkdll.com, ns500742.ns500754.ns500731.ns500671.ns500671.ns500742.ns500671.ns500704.ns500704.ns500705.ns500678.ns500688.ns500649.ns500649.lustychickser.com, rixincosmetics.com and ns500698.ns500698.ns500698.ns500758.ns500736.ns500698.ns500735.ns500736.ns500698.ns500698.ns500735.ns500698.ns500619.ns500686.ns500619.trackreceptor.com.
Mail servers frequently appear alongside alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host aspmx2.googlemail.com points to 2800:3f0:4003:c0f::1a and 108.177.123.26
Host aspmx3.googlemail.com points to 2a00:1450:400b:c02::1a and 172.253.116.27
Host aspmx.l.google.com points to 2607:f8b0:4004:c1f::1a and 172.253.63.27
Host alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1a and 108.177.123.26
Host alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.27
Hosts pointing to 2800:3f0:4003:c0f::1a: aspmx2.googlemail.com and alt1.aspmx.l.google.com
Hosts pointing to 108.177.123.26: aspmx2.googlemail.com and alt1.aspmx.l.google.com
Hosts pointing to 2a00:1450:400b:c02::1a: aspmx3.googlemail.com and alt2.aspmx.l.google.com
Hosts pointing to 172.253.116.27: aspmx3.googlemail.com and alt2.aspmx.l.google.com
Pattern: 2800:3f0:4003:c0f::1a and 108.177.123.26 appear with aspmx2.googlemail.com and alt1.aspmx.l.google.com; 2a00:1450:400b:c02::1a and 172.253.116.27 appear with aspmx3.googlemail.com and alt2.aspmx.l.google.com