Skip to content

Hostname

spusu.ch

Last fetched

spusu.ch resolves to 193.9.252.215, announced in 193.9.252.0/24 by MASSRESPONSE-AS - Mass Response Service GmbH in AT. spusu.ch 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 · spusu.chRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/spusu.ch

Resolution chain

IPv6 resolution

No AAAA record for spusu.ch is recorded in WhisperGraph.

Attribution

mass response

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for spusu.ch. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
dns1.spusu.ch
wildcard.spusu.ch
www.spusu.ch

Showing 3 of 3 subdomains (3 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.massresponse.com
  • ns2.massresponse.com
  • ns3.massresponse.com
  • ns4.massresponse.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

  • mail-proxy.massresponse.com
  • mail-proxy2.massresponse.com

SPF policy

  • ip: 193.9.252.0/23
  • a: spusu.ch
  • mx: spusu.ch
  • include: spf.protection.outlook.com
  • ip: 176.126.39.8
  • ip: 62.240.131.200

Threat-feed evidence

History

Related pages

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