Skip to content

Hostname

landscapeuganda.com

Last fetched

landscapeuganda.com resolves to 213.136.83.235, announced in 213.136.82.0/23 by CONTABO - Contabo GmbH in DE. landscapeuganda.com is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Sat, 12 Sep 2026 00:46:38 GMT

Nutrition Label

WHISPER CANON · landscapeuganda.comRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency6.7/10Resolver footprint9.2/10canon.whisper.security/host/landscapeuganda.com

Resolution chain

IPv6 resolution

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

Attribution

contabo

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:472

Subdomains

Showing 1 of 1 subdomain (1 per page).

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

  • ns15.momentumhosting.cloud
  • ns16.momentumhosting.cloud
  • ns25.momentumhosting.cloud
  • ns26.momentumhosting.cloud
  • ns35.momentumhosting.cloud
  • ns36.momentumhosting.cloud
  • ns45.momentumhosting.cloud
  • ns46.momentumhosting.cloud
  • ns55.momentumhosting.cloud
  • ns56.momentumhosting.cloud
  • 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

  • landscapeuganda.com

SPF policy

  • a: landscapeuganda.com
  • mx: landscapeuganda.com
  • ip: 213.136.83.235

Threat-feed evidence

History

Related pages

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