Skip to content

Hostname

flixbus.hu

Last fetched

flixbus.hu resolves to 108.138.51.127, announced in 108.138.48.0/21 by AMAZON-02 - Amazon.com, Inc. in IE. flixbus.hu 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 · flixbus.huRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/flixbus.hu

Resolution chain

IPv6 resolution

No AAAA record for flixbus.hu is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for flixbus.hu. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
help-dev.flixbus.hu
help.flixbus.hu
shop-dev.flixbus.hu
shop.flixbus.hu
stage-www.flixbus.hu
www-dev.flixbus.hu
www.flixbus.hu

Showing 7 of 7 subdomains (7 per page).

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

  • ns-366.awsdns-45.com
  • ns-801.awsdns-36.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
  • ns-1158.awsdns-16.org
  • ns-1770.awsdns-29.co.uk

MX records

  • flixbus-hu.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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