Skip to content

Hostname

belegend.jp

Last fetched

belegend.jp resolves to 157.112.182.152, announced in 157.112.176.0/21 by XSERVER - Xserver Inc. in JP. belegend.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 · belegend.jpRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.5/10canon.whisper.security/host/belegend.jp

Resolution chain

IPv6 resolution

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

Attribution

xserver

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrant organisation
gmo pepabo,
Contact emails
admin@muumuu-domain.com

Subdomains

Subdomain
_dmarc.belegend.jp
_mta-sts.belegend.jp
belegend2019.belegend.jp
business.belegend.jp
mta-sts.belegend.jp
ore.belegend.jp
sb.belegend.jp
sports.belegend.jp
store.belegend.jp
www.belegend.jp

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

  • ns1.xserver.jp
  • ns2.xserver.jp
  • ns3.xserver.jp
  • ns4.xserver.jp
  • ns5.xserver.jp
  • 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

  • belegend-jp.mail.protection.outlook.com
  • belegend.jp

SPF policy

  • include: spf.mta.hdems.com
  • include: spf.protection.outlook.com
  • include: spf1.bcart.jp
  • include: send.k-crm.jp
  • include: ml_spf_g2.mlritz.net

Threat-feed evidence

History

Related pages

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