Skip to content

Hostname

angry.space

Last fetched

angry.space resolves to 84.201.159.102, announced in 84.201.128.0/18 by YandexCloud - Yandex.Cloud LLC in RU. angry.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 · angry.spaceRouting diversity1.5/10Peering density5.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint5.6/10canon.whisper.security/host/angry.space

Resolution chain

IPv6 resolution

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

Attribution

Yandex

esp · ORIGIN_AS

WHOIS identity

Registrar
iana:1606
Registrant organisation
privacy protection

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

  • ns1.yandexcloud.net
  • ns2.yandexcloud.net
  • ns1.selectel.ru
  • ns2.selectel.ru
  • ns3.selectel.ru
  • ns4.selectel.ru

MX records

  • emx.mail.ru

SPF policy

  • ip: 5.189.238.160/29
  • ip: 82.202.222.176/29
  • ip: 89.248.196.192/28
  • ip: 82.202.205.80/29
  • include: mxsspf.sendpulse.com
  • include: _spf.mail.ru
  • include: spf.mail.selcloud.ru
  • a: angry.space
  • mx: angry.space

Threat-feed evidence

History

Related pages

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