Skip to content

Hostname

player.zone

Last fetched

player.zone resolves to 194.247.186.42, announced in 194.247.186.0/24 by HOSTKEY-AS - HOSTKEY B.V. in DE. player.zone 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 · player.zoneRouting diversity1.5/10Peering density7.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/player.zone

Resolution chain

IPv6 resolution

No AAAA record for player.zone is recorded in WhisperGraph.

Attribution

hostkey

ORIGIN_AS

WHOIS identity

Registrar
iana:472
Registrant organisation
it solutions maciej zdziarstek
Contact emails
wago442udcbhr7k9v2gx@o.o-w-o.info, z8t06b8v7td4860p60nb@t.o-w-o.info

Subdomains

Subdomain
cdn.player.zone
dev.player.zone
www.player.zone

Showing 3 of 4. View all subdomains →

Mail and authentication

Nameservers

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

MX records

  • mx.yandex.net

SPF policy

  • include: _spf.yandex.net
  • ip: 2.58.67.152

Threat-feed evidence

History

Related pages

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