Skip to content

Hostname

leber.jp

Last fetched

leber.jp resolves to 13.227.192.23, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. leber.jp 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 · leber.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/leber.jp

Resolution chain

IPv6 resolution

No AAAA record for leber.jp is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
(not displayed by registrant's request)
Contact emails
proxy@whoisprotectservice.com

Subdomains

Subdomain
analytics.leber.jp
console.leber.jp
data.leber.jp
dev-online-medical-api.leber.jp
dev-online-medical.leber.jp
dev.leber.jp
l.leber.jp
leber.leber.jp
lp.leber.jp
mg.leber.jp
online-medical-api.leber.jp
recruit.leber.jp

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

  • ns-226.awsdns-28.com
  • ns-825.awsdns-39.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
  • ns-1182.awsdns-19.org
  • ns-1678.awsdns-17.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: 1lejend.com
  • include: _spf.elasticemail.com
  • include: _spf.google.com
  • include: 6064293.spf05.hubspotemail.net

Threat-feed evidence

History

Related pages

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