Skip to content

Hostname

roteerdbeere.com

Last fetched

roteerdbeere.com resolves to 31.214.242.135, announced in 31.214.242.0/24 by ACTIVE-SERVERS - active 1 GmbH in DE. roteerdbeere.com 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 · roteerdbeere.comRouting diversity1.5/10Peering density6.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/roteerdbeere.com

Resolution chain

IPv6 resolution

No AAAA record for roteerdbeere.com is recorded in WhisperGraph.

Attribution

active

ORIGIN_AS

WHOIS identity

Registrar
iana:1328
Registrant organisation
alexis mesa marrero
Contact emails
webmaster@roteerdbeere.com, info@domain-contact.org

Subdomains

Subdomain
ai.roteerdbeere.com
app.roteerdbeere.com
buchhaltung.roteerdbeere.com
mail.roteerdbeere.com
search.roteerdbeere.com
www.roteerdbeere.com

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

Sample outbound links

Mail and authentication

Nameservers

  • 1.ns-ebiz.de
  • 2.ns-ebiz.de
  • 3.ns-ebiz.de
  • 4.ns-ebiz.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

MX records

  • mail.roteerdbeere.com

SPF policy

  • a: roteerdbeere.com
  • mx: roteerdbeere.com
  • include: spf.ebiz-webhosting.de

Threat-feed evidence

History

Related pages

Pivot from roteerdbeere.com 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: "roteerdbeere.com"})-[: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.