flagsucker.com - dns.ninja

flagsucker.com

DNSSEC⚠️ Not signed
A72.9.100.58πŸ‡ΊπŸ‡Έ EZZI-101-BGP72.9.96.0/20 EZZI.net ROUTE
PTRmail.f11.org
NSflagsucker.com ⭐
A72.9.100.58πŸ‡ΊπŸ‡Έ EZZI-101-BGP72.9.96.0/20 EZZI.net ROUTE
PTRmail.f11.org
NSa.bitless.net
A72.9.100.58πŸ‡ΊπŸ‡Έ EZZI-101-BGP72.9.96.0/20 EZZI.net ROUTE
PTRmail.f11.org
NSa.f11.org
A72.9.100.61πŸ‡ΊπŸ‡Έ EZZI-101-BGP72.9.96.0/20 EZZI.net ROUTE
PTRmail.bitless.net
MXmail.bitless.net ⭐
A72.9.100.61πŸ‡ΊπŸ‡Έ EZZI-101-BGP72.9.96.0/20 EZZI.net ROUTE
PTRmail.bitless.net
MXmail.f11.org(20)
A72.9.100.58πŸ‡ΊπŸ‡Έ EZZI-101-BGP72.9.96.0/20 EZZI.net ROUTE
PTRmail.f11.org
SOAflagsucker.comhostmaster@bitless.net 2006-10-16 #1

com

WOT: SUSPICIOUS (1/100)

NS for

Same first word

DNS History

6 records (6 active, 0 former)

20162017201820192020202120222023202420252026NSa.bitless.neta.f11.orgflagsucker.comMXmail.bitless.netmail.f11.orgA72.9.100.58
●NSa.bitless.net2015-05-16 β†’ 2026-08-08 Β· 2 obs
● 2015-05-16 18:38:58
● 2026-08-08 14:19:02
●NSa.f11.org2015-05-16 β†’ 2026-08-08 Β· 2 obs
● 2015-05-16 18:38:58
● 2026-08-08 14:19:02
●NSflagsucker.com2015-05-16 β†’ 2026-08-08 Β· 2 obs
● 2015-05-16 18:38:58
● 2026-08-08 14:19:02
●MXmail.bitless.net2015-05-16 β†’ 2026-08-08 Β· 2 obs
● 2015-05-16 18:38:58
● 2026-08-08 14:19:02
●MXmail.f11.org2015-05-16 β†’ 2026-08-08 Β· 2 obs
● 2015-05-16 18:38:58
● 2026-08-08 14:19:02
●A72.9.100.582015-05-16 β†’ 2026-08-08 Β· 2 obs
● 2015-05-16 18:38:58
● 2026-08-08 14:19:02

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
flagsucker.coma.bitless.net, a.f11.org-

βœ… Authoritative Response

Server:72.9.100.61

NS records: a.bitless.net, a.f11.org

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flagsucker.com (unsigned zone)

⏱️ Timing

Total: 207ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A172.9.100.58
NS2a.f11.org, a.bitless.net
MX2mail.bitless.net (pri: 10), mail.f11.org (pri: 20)
SOA1flagsucker.com hostmaster.bitless.net

Analysis

Name Server Role

flagsucker.com acts as a name server for flagsucker.com, meaning it is self-referentially delegated.

The name servers a.bitless.net and a.f11.org are often paired with flagsucker.com.

IP Addresses

flagsucker.com resolves to one IP address: 72.9.100.58.

fil.nyc, thinkevil.com, attakh.net and two other host names share IP numbers with flagsucker.com.

Name Servers

The DNS delegation for flagsucker.com uses three name servers β€” flagsucker.com, a.bitless.net and a.f11.org.

flagsucker.com has at least partial name server overlap with other domains, such as f11.org, fil.nyc, thinkevil.com and two others.

ugly.teofen.com, intldef.org and variousdirections.com β€” plus 6 other name servers β€” are commonly paired with these name servers.

Each of the three hostnames β€” flagsucker.com, a.bitless.net and a.f11.org β€” has a single IP address. flagsucker.com and a.bitless.net resolve to 72.9.100.58; a.f11.org resolves to 72.9.100.61.

The host names flagsucker.com and a.bitless.net both resolve to 72.9.100.58 IP addresses.

Mail Servers

Mail for flagsucker.com is handled by two mail servers β€” mail.bitless.net and mail.f11.org.

flagsucker.com uses an identical mail server configuration to several other domains β€” among them passalongbooks.org, uglycomputer.com, bitless.net and two more.

The mail servers of flagsucker.com are at least partially shared with other domains, including vacantlook.com.

mail.bitless.net directs to 72.9.100.61 and mail.f11.org directs to 72.9.100.58; each host name points to exactly one IP number.