Skip to content

Hostname

sailormoon-store.com

Last fetched

sailormoon-store.com resolves to 108.158.251.114, announced in 108.158.251.0/24 by AMAZON-02 - Amazon.com, Inc. in SG. sailormoon-store.com 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 · sailormoon-store.comRouting diversity1.5/10Peering density9.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/sailormoon-store.com

Resolution chain

IPv6 resolution

No AAAA record for sailormoon-store.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of sailormoon-store.com owner
Contact emails
157a7901-b905-4f17-abd0-e749fb75a392@identity-protect.org, 2f921b71-427a-43d0-8c7d-9eeacd23ad7f@identity-protect.org, 4a5b473a-71b9-4849-a5b6-034762c50538@identity-protect.org, ceeade64-2310-4dd8-8af9-3e56c0a4ca84@identity-protect.org, e1d9d48b-b2f0-45bc-9279-2acac6300878@identity-protect.org, ee51fa36-b122-4ac8-b3c3-ce600f26dc39@identity-protect.org, owner-672718@sailormoon-store.com.whoisprivacyservice.org

Subdomains

Subdomain
www.sailormoon-store.com

Showing 1 of 1 subdomain (1 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

  • ns-43.awsdns-05.com
  • ns-783.awsdns-33.net
  • ns-1516.awsdns-61.org
  • ns-1787.awsdns-31.co.uk

MX records

  • mx.securemx.jp

SPF policy

  • include: spf.ecbeing.co.jp
  • include: asp.cuenote.jp
  • include: md37.maildealer.jp
  • include: spf.q-send.jp
  • include: spf.securemx.jp

Threat-feed evidence

History

Related pages

Pivot from sailormoon-store.com 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: "sailormoon-store.com"})-[: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.