Skip to content

Hostname

regiolux.de

Last fetched

regiolux.de resolves to 85.237.86.249, announced in 85.237.84.0/22 by PHADE-AS - Frank Gadegast trading as PHADE Software in DE. regiolux.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 · regiolux.deRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/regiolux.de

Resolution chain

IPv6 resolution

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

Attribution

frank gadegast trading phade software

ORIGIN_AS

WHOIS identity

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

  • ns3.phade.de
  • 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
  • ns1.powerweb.zone

MX records

  • mx-62728249.mail.eu.retarus.com
  • mx-in01.eu.retarus.com

SPF policy

  • ip: 193.158.225.160/29
  • ip: 85.237.86.240/28
  • include: spf.protection.outlook.com
  • include: _spf.retarus.com
  • include: _spf.senders.scnem.com
  • a: event.regiolux.de
  • a: 2nd.powerweb.mx

Threat-feed evidence

History

Related pages

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