Skip to content

Hostname

gamesys.co.uk

Last fetched

gamesys.co.uk resolves to 104.21.64.240, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. gamesys.co.uk 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 · gamesys.co.ukRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/gamesys.co.uk

Resolution chain

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

Registrar
registrar:csc corporate domains, inc [tag = csc-corp-domains]
Registrant organisation
gamesys

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • art.ns.cloudflare.com
  • gene.ns.cloudflare.com
  • 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

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 93.93.82.1/32
  • ip: 93.93.83.1/32
  • ip: 93.93.85.1/32
  • ip: 93.93.86.1/32
  • ip: 93.93.84.151/32
  • ip: 93.93.84.17/32
  • ip: 185.86.45.211/32
  • ip: 93.93.84.40/32
  • include: us._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

Pivot from gamesys.co.uk 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: "gamesys.co.uk"})-[: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.