Skip to content

Hostname

rib.de

Last fetched

rib.de resolves to 149.232.252.19, announced in 149.232.252.0/22 by INGENIT - Marc-Christian Schroeer trading as 'ingenit GmbH & Co. KG' in DE. rib.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 · rib.deRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/rib.de

Resolution chain

IPv6 resolution

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

Attribution

marc christian schroeer trading ingenit

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for rib.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
account.rib.de
d.rib.de
dortmund.rib.de
dtag-2m.rib.de
dtag-gw.rib.de
itwotender.rib.de
meinauftrag.rib.de
mx01.rib.de
myorder.rib.de
server01.rib.de
spf-evergabe.rib.de
vergabe.rib.de

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

  • ns2-eu.123ns.de
  • ns4-eu.123ns.de
  • ns1-eu.123ns.eu
  • ns3-eu.123ns.eu

MX records

  • de-smtp-inbound-1.mimecast.com
  • de-smtp-inbound-2.mimecast.com
  • rib-de.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: spf-germany.rib-software.com
  • include: spf-evergabe.rib.de

Threat-feed evidence

History

Related pages

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