Skip to content

Hostname

playgwent.com

Last fetched

playgwent.com resolves to 185.2.115.175, announced in 185.2.112.0/22 by ATMAN - Atman Sp. z o.o. in PL. playgwent.com 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 · playgwent.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/playgwent.com

Resolution chain

IPv6 resolution

No AAAA record for playgwent.com is recorded in WhisperGraph.

Attribution

atman sp

ORIGIN_AS

WHOIS identity

Registrar
iana:1456
Registrant organisation
whois data protection sp. z o.o.
Contact emails
twadmins@cdprojektred.com, bktrdcmkeyoe-r@mail.whoisdataprotection.com, iunuxhghalwx-r@mail.whoisdataprotection.com, ktjygjevacat-r@mail.whoisdataprotection.com, maavempxiqsx-r@mail.whoisdataprotection.com, nrnfleipdcml-r@mail.whoisdataprotection.com, ovvvbawadgld-r@mail.whoisdataprotection.com, qjruvyejvass-r@mail.whoisdataprotection.com, rlmybpfgoxph-r@mail.whoisdataprotection.com, youtrolpbxrd-r@mail.whoisdataprotection.com, 499432423d777123308a99570270194b-1614700@contact.gandi.net

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • garrett.ns.cloudflare.com
  • lilith.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com

SPF policy

  • ip: 91.222.185.194/31
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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