Skip to content

Hostname

brasty.hr

Last fetched

brasty.hr resolves to 104.21.51.241, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. brasty.hr 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 · brasty.hrRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint3.2/10canon.whisper.security/host/brasty.hr

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:euronet
Registrant organisation
brasty group s.r.o.
Contact emails
admin@brasty.com

Subdomains

Subdomain
beauty.brasty.hr
pre.brasty.hr
test.brasty.hr
test1.brasty.hr
test10.brasty.hr
test2.brasty.hr
test3.brasty.hr
test4.brasty.hr
test5.brasty.hr
test6.brasty.hr
test7.brasty.hr
test8.brasty.hr

Showing 12 of 14. 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

  • damon.ns.cloudflare.com
  • meera.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 217.198.120.0/20
  • ip: 213.109.165.0/24
  • ip: 213.109.167.0/24
  • include: _spf.google.com
  • ip: 149.72.137.202
  • ip: 178.248.13.29
  • ip: 185.59.210.243
  • ip: 185.59.210.251
  • ip: 185.59.211.161
  • ip: 185.59.211.162
  • ip: 185.59.211.163
  • ip: 185.59.211.181
  • ip: 185.59.211.182
  • ip: 185.59.211.183
  • ip: 185.59.211.184
  • ip: 185.59.211.185
  • ip: 217.16.185.19
  • ip: 46.227.170.113
  • ip: 49.72.83.149
  • ip: 93.185.111.247

Threat-feed evidence

History

Related pages

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