Skip to content

Hostname

rupprecht.de

Last fetched

rupprecht.de resolves to 18.153.0.93, announced in 18.153.0.0/16 by AMAZON-02 - Amazon.com, Inc. in DE. rupprecht.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 · rupprecht.deRouting diversity2.4/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/rupprecht.de

Resolution chain

IPv6 resolution

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

Attribution

plusserver

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for rupprecht.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
cloud.rupprecht.de
ebooks.rupprecht.de
libriapi.rupprecht.de
mailsrv.rupprecht.de
mx-in-1.rupprecht.de
mx-in-2.rupprecht.de
smtprelay.rupprecht.de
webmail.rupprecht.de
www.rupprecht.de

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

Mail and authentication

Nameservers

  • robotns3.second-ns.com
  • ns1.first-ns.de
  • robotns2.second-ns.de

MX records

  • mx-in-1.rupprecht.de
  • mx-in-2.rupprecht.de

SPF policy

  • a: mailrelay01.ext.nexinto.com
  • a: mailrelay02.ext.nexinto.com
  • a: mailrelay.nexinto.com
  • mx: rupprecht.de
  • a: smtprelay.rupprecht.de

Threat-feed evidence

History

Related pages

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