Skip to content

Hostname

promostore.de

Last fetched

promostore.de resolves to 167.235.109.60, announced in 167.235.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. promostore.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 · promostore.deRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/promostore.de

Resolution chain

IPv6 resolution

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for promostore.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

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

  • clara.ns.cloudflare.com
  • grant.ns.cloudflare.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

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

SPF policy

  • include: spf.protection.outlook.com
  • a: promostore.de
  • mx: promostore.de
  • a: dedi2078.your-server.de
  • a: dedi6399.your-server.de
  • a: dedivirt2788.your-server.de
  • include: spf.strold.io
  • include: 139607031.spf04.hubspotemail.net
  • ip: 159.69.47.10
  • ip: 2a01:4f8:c0c:f2ce:0:0:0:1
  • ip: 5.75.183.99
  • ip: 91.107.230.226

Threat-feed evidence

History

Related pages

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