Skip to content

Hostname

udsgame.com

Last fetched

udsgame.com resolves to 78.155.217.100, announced in 78.155.217.0/24 by SELECTEL-MSK - JSC Selectel in RU. udsgame.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 · udsgame.comRouting diversity3.0/10Peering density6.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/udsgame.com

Resolution chain

IPv6 resolution

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

Attribution

jsc selectel

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of udsgame.com owner
Contact emails
udsgame.com@domainsbyproxy.com, 47517f87-acd6-4976-9156-5df66e48b0f4@identity-protect.org, 6b75eaaf-5f47-40cc-aff5-4e5f3a7a355e@identity-protect.org, afbcb01b-a728-4153-94dc-e012eec1f666@identity-protect.org, f0e42438-86d0-4716-966e-a4fc8bc538ab@identity-protect.org

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

  • cruz.ns.cloudflare.com
  • skip.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

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

SPF policy

  • include: amazonses.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from udsgame.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: "udsgame.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.