Skip to content

Hostname

transfermarkt.world

Last fetched

transfermarkt.world resolves to 5.159.57.194, announced in 5.159.56.0/21 by TLN-AS - terralink networks GmbH in DE. transfermarkt.world 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 · transfermarkt.worldRouting diversity2.4/10Peering density5.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/transfermarkt.world

Resolution chain

IPv6 resolution

No AAAA record for transfermarkt.world is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1408
Registrant organisation
transfermarkt gmbh & co. kg
Contact emails
domains@transfermarkt.de

Subdomains

Subdomain
cp.transfermarkt.world
data-1c0a3d83e3.transfermarkt.world
data-84a0f3455d.transfermarkt.world
rechenschieber.transfermarkt.world
www.transfermarkt.world

Showing 5 of 5 subdomains (5 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

Mail and authentication

Nameservers

  • pns21.cloudns.net
  • pns22.cloudns.net
  • pns23.cloudns.net
  • pns24.cloudns.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

  • transfermarkt-world.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • a: mail01.transfermarkt.de
  • a: mail02.transfermarkt.de
  • a: transfermarkt.world
  • mx: transfermarkt.world

Threat-feed evidence

History

Related pages

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