Skip to content

Hostname

digimerce.jp

Last fetched

digimerce.jp resolves to 13.230.75.112, announced in 13.230.0.0/15 by AMAZON-02 - Amazon.com, Inc. in JP. digimerce.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 · digimerce.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/digimerce.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
digimerce
Contact emails
info@digimerce.jp

Subdomains

Subdomain
blog.digimerce.jp
gift.digimerce.jp
ml.digimerce.jp
mx.digimerce.jp
recruit.digimerce.jp
regist-staging.digimerce.jp
regist.digimerce.jp
www.digimerce.jp

Showing 8 of 11. 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

  • 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
  • ns1.shsvr.net
  • ns2.shsvr.net

MX records

  • mx.digimerce.jp

SPF policy

  • ip: 218.216.135.0/24
  • include: mail-spf.ferret-one.com
  • include: spf.satorimail.net
  • include: _spf.shared-server.net
  • ip: 43.206.15.153

Threat-feed evidence

History

Related pages

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