Skip to content

Hostname

geoma.space

Last fetched

geoma.space resolves to 158.160.122.54, announced in 158.160.0.0/16 by YandexCloud - Yandex.Cloud LLC in RU. geoma.space 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 · geoma.spaceRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/geoma.space

Resolution chain

IPv6 resolution

No AAAA record for geoma.space is recorded in WhisperGraph.

Attribution

Yandex

esp · ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
see privacyguardian.org

Subdomains

Subdomain
music.geoma.space
mws1.geoma.space
storage.geoma.space
test.geoma.space
turn2.geoma.space
v2.geoma.space
ws.geoma.space
ws1.geoma.space
ws2.geoma.space
ws3.geoma.space

Showing 10 of 11. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.yandexcloud.net
  • ns2.yandexcloud.net

MX records

  • mx.yandex.net

SPF policy

  • include: spf.smtp.bz
  • redirect: _spf.yandex.net
  • a: geoma.space
  • mx: geoma.space

Threat-feed evidence

History

Related pages

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