Skip to content

Hostname

mu-mo.net

Last fetched

mu-mo.net resolves to 13.227.192.49, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. mu-mo.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 · mu-mo.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/mu-mo.net

Resolution chain

IPv6 resolution

No AAAA record for mu-mo.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:49
Registrant organisation
avex music creative.inc.
Contact emails
ami-sysdom@av.avex.co.jp

Subdomains

Subdomain
adm-shop-play.mu-mo.net
adm-shop-stage.mu-mo.net
adm-shop.mu-mo.net
ani.mu-mo.net
az.mu-mo.net
dtc.mu-mo.net
img-shop.mu-mo.net
kuriki.mu-mo.net
login-gigya.mu-mo.net
m-shop-dev.mu-mo.net
m-shop-dev2.mu-mo.net
m-shop-play.mu-mo.net

Showing 12 of 66. 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-96.awsdns-12.com
  • ns-815.awsdns-37.net
  • ns-1163.awsdns-17.org
  • ns-2029.awsdns-61.co.uk

MX records

  • mxacloud02.imatrix.co.jp

SPF policy

  • ip: 210.136.114.0/24
  • ip: 210.153.83.0/24
  • ip: 211.13.209.192/26
  • ip: 211.13.207.64/26
  • include: bmsend.com
  • include: cnfc.avex.jp
  • a: misc-mail01.avex.jp
  • include: srs2389.cuenote.jp
  • include: mds3168.maildealer.jp
  • ip: 203.191.225.177
  • ip: 211.13.209.240
  • ip: 211.13.209.241
  • ip: 222.151.206.179

Threat-feed evidence

History

Related pages

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