Skip to content

Hostname

weverseshop.io

Last fetched

weverseshop.io resolves to 13.124.1.93, announced in 13.124.0.0/16 by AMAZON-02 - Amazon.com, Inc. in KR. weverseshop.io 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 · weverseshop.ioRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/weverseshop.io

Resolution chain

IPv6 resolution

No AAAA record for weverseshop.io is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:244
Registrant organisation
weverse company

Subdomains

Subdomain
about.weverseshop.io
api.weverseshop.io
campaign.weverseshop.io
campaigns.weverseshop.io
cardadmin-int.weverseshop.io
cardadmin.weverseshop.io
cdn-contents.weverseshop.io
desk.weverseshop.io
id.weverseshop.io
share.weverseshop.io
webcontents.weverseshop.io
weversecardeapi.weverseshop.io

Showing 12 of 14. 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-66.awsdns-08.com
  • ns-914.awsdns-50.net
  • ns-1523.awsdns-62.org
  • ns-1950.awsdns-51.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: amazonses.com
  • include: _spf.google.com
  • include: shops.shopify.com
  • include: spf.baremetal.jp
  • include: spf.haihaimail.jp

Threat-feed evidence

History

Related pages

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