Hostname

leakzone.net

Last fetched Thu, 17 Sep 2026 13:31:22 GMT

leakzone.net resolves to 142.44.133.80, announced in 142.44.128.0/17 by OVH - OVH SAS in CA. leakzone.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

Resolution chain

142.44.133.80
142.44.128.0/17 · OVH - OVH SAS
142.44.156.130
142.44.128.0/17 · OVH - OVH SAS · Kennesaw, US
172.234.24.211
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.239.57.117
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
51.195.166.167
51.195.0.0/16 · OVH - OVH SAS · London, GB
51.75.175.17
51.75.0.0/16 · OVH - OVH SAS · London, GB
51.81.253.205
51.81.128.0/17 · OVH - OVH SAS · Reston, US
51.81.254.6
51.81.128.0/17 · OVH - OVH SAS · Reston, US

IPv6 resolution

No AAAA record for leakzone.net is recorded in WhisperGraph.

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar: iana:1068
Registrant organisation: domains by proxy,
Contact emails: leakzone.net@domainsbyproxy.com, d6aa13c45ae5466d8ec1c4260d045936.protect@whoisguard.com, 7bdc96c908f24f2195d7822ae306c55d.protect@withheldforprivacy.com, fea079e233a14a0e9469946006970eb1.protect@withheldforprivacy.com

Subdomains

Subdomain
mail.leakzone.net
pay.leakzone.net
shorrtr.leakzone.net
www.leakzone.net

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

Mail and authentication

Nameservers

jill.ns.cloudflare.com
micah.ns.cloudflare.com

MX records

mail.leakzone.net

SPF policy

mx: leakzone.net

Threat-feed evidence

History

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