Skip to content

Hostname

flaunt.nu

Last fetched

flaunt.nu resolves to 185.38.248.201, announced in 185.38.248.0/22 by SPRINT-SDC - "SPRINT" S.A. in PL. flaunt.nu 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 · flaunt.nuRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/flaunt.nu

Resolution chain

IPv6 resolution

No AAAA record for flaunt.nu is recorded in WhisperGraph.

Attribution

sprint

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:key-systems
Registrant organisation
farley lyn go
Contact emails
wacky_lokpo@yahoo.com

Subdomains

Subdomain
ad.flaunt.nu
adamcolesource.flaunt.nu
adelaidekanebr.flaunt.nu
admin.flaunt.nu
adopt.flaunt.nu
adoring-dmjohnson.flaunt.nu
adoringhenrycavill.flaunt.nu
aemydesign.flaunt.nu
alexaweird.flaunt.nu
alilarterfan.flaunt.nu
allthingsackles.flaunt.nu
amandaseyfriedbr.flaunt.nu

Showing 12 of 2,173. 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

Mail and authentication

Nameservers

  • ns1.fans-planet.com
  • ns2.fans-planet.com
  • us1.flauntmedia.net
  • us2.flauntmedia.net
  • 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

  • flaunt.nu

SPF policy

  • a: flaunt.nu
  • mx: flaunt.nu
  • ip: 185.38.248.201
  • ip: 185.38.249.79
  • ip: 46.29.20.178

Threat-feed evidence

History

Related pages

Pivot from flaunt.nu 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: "flaunt.nu"})-[: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.