Skip to content

Hostname

mesem.de

Last fetched

mesem.de resolves to 104.26.14.4, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. mesem.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 · mesem.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/mesem.de

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mesem.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
chat.mesem.de
cloud.mesem.de
extern.mesem.de
git.mesem.de
info.mesem.de
lager.mesem.de
lux.mesem.de
mail.mesem.de
mesem.mesem.de
office.mesem.de
proxy.mesem.de
test.mesem.de

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

  • harvey.ns.cloudflare.com
  • jean.ns.cloudflare.com
  • nsa3.schlundtech.de
  • nsb3.schlundtech.de
  • nsc3.schlundtech.de
  • nsd3.schlundtech.de

MX records

  • mail.mesem.de

SPF policy

  • ip: 85.13.133.129/32
  • ip: 185.65.192.196/32
  • ip: 82.198.70.242/32
  • ip: 213.164.158.42/32
  • include: spf.mailjet.com
  • include: mail.zendesk.com
  • include: _spf.gatworks.de
  • a: mesem.de
  • mx: mesem.de

Threat-feed evidence

History

Related pages

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