Skip to content

Hostname

flagma.uz

Last fetched

flagma.uz resolves to 207.180.210.225, announced in 207.180.210.0/23 by CONTABO - Contabo GmbH in DE. flagma.uz is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · flagma.uzRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.2/10canon.whisper.security/host/flagma.uz

Resolution chain

IPv6 resolution

No AAAA record for flagma.uz is recorded in WhisperGraph.

Attribution

contabo

ORIGIN_AS

WHOIS identity

Registrar
registrar:bcc
Registrant organisation
not.defined. a. rylskiy (domains [at] rwgusa.com )

Subdomains

Subdomain
admin.flagma.uz
ahangaran.flagma.uz
alat.flagma.uz
almalyk.flagma.uz
almazar.flagma.uz
andizhan.flagma.uz
andizhanskayaoblast.flagma.uz
angren.flagma.uz
asakauzbek.flagma.uz
bekabad.flagma.uz
beshkent.flagma.uz
boz.flagma.uz

Showing 12 of 83. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.101domain.com
  • ns2.101domain.com
  • ns5.101domain.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mail.flagma.uz

SPF policy

  • mx: flagma.uz

Threat-feed evidence

History

Related pages

Pivot from flagma.uz into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "flagma.uz"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.