Skip to content

Hostname

hse.de

Last fetched

hse.de resolves to 104.126.37.128, announced in 104.126.36.0/23 by AKAMAI-ASN1 - Akamai International B.V. in DE. hse.de 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 · hse.deRouting diversity1.5/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/hse.de

Resolution chain

IPv6 resolution

No AAAA record for hse.de is recorded in WhisperGraph.

Attribution

akamai international

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for hse.de. 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
app.hse.de
development.hse.de
devops.hse.de
hello.hse.de
info.hse.de
measurement-preview.hse.de
measurement.hse.de
news.hse.de
newsletter.hse.de
qas.hse.de
sgtm.hse.de
shop.hse.de

Showing 12 of 16. 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

  • a1-156.akam.net
  • a13-65.akam.net
  • a14-66.akam.net
  • a18-67.akam.net
  • a24-64.akam.net
  • a7-65.akam.net

MX records

  • hse-de.mail.protection.outlook.com

SPF policy

  • ip: 185.215.216.0/24
  • ip: 185.215.217.0/24
  • ip: 185.93.143.0/26
  • ip: 195.10.208.0/26
  • ip: 2001:67c:2050:102:465::/80
  • ip: 193.28.100.68/32
  • include: inxserver.com
  • include: spf.protection.outlook.com
  • include: _spf.general.transactional-mail-a.com
  • a: hse.de
  • a: mx01.rexx-systems.de

Threat-feed evidence

History

Related pages

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