Skip to content

Hostname

rezel.net

Last fetched

rezel.net resolves to 137.194.15.86, announced in 137.194.0.0/16 by FR-RENATER-ENST - Renater in FR. rezel.net 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 · rezel.netRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/rezel.net

Resolution chain

IPv6 resolution

Attribution

renater

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
association rezel
Contact emails
00d29f8b0089e1fe3a383676f9afd449-40139964@contact.gandi.net, 6dc77341a7bc713025251e9f25b654cf-40139964@contact.gandi.net, bb2fac760561cd74621cd87511201c6d-ar1273@contact.gandi.net

Subdomains

Subdomain
adh.rezel.net
alpha.rezel.net
apps.rezel.net
ayiana.rezel.net
babar.rezel.net
bde-dev.rezel.net
bds-web.rezel.net
beta.rezel.net
ca.rezel.net
cert.rezel.net
chat.rezel.net
chat2.rezel.net

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

Mail and authentication

Nameservers

  • ns0.rezel.net
  • ns1.rezel.net
  • ns2.rezel.net
  • 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.rezel.net

SPF policy

  • mx: rezel.net

Threat-feed evidence

History

Related pages

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