Skip to content

Hostname

l33.fr

Last fetched

l33.fr resolves to 212.129.33.72, announced in 212.129.0.0/18 by AS12876 - Scaleway SAS in FR. l33.fr 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 · l33.frRouting diversity1.5/10Peering density6.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/l33.fr

Resolution chain

IPv6 resolution

No AAAA record for l33.fr is recorded in WhisperGraph.

Attribution

scaleway

ORIGIN_AS

WHOIS identity

Registrar
registrar:gandi
Registrant organisation
l33 networks
Contact emails
230cb73c1b009d418ed09d7e3c650097-1166980@contact.gandi.net

Subdomains

Subdomain
co3.l33.fr
crm.l33.fr
mail.l33.fr
ns2.l33.fr
ns3.l33.fr
ns4.l33.fr
ns5.l33.fr
virt1-par2.l33.fr
www.l33.fr

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

Sample outbound links

Mail and authentication

Nameservers

  • ns2.l33.fr
  • ns3.l33.fr
  • ns4.l33.fr
  • ns6.gandi.net
  • ns5.he.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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