Hostname
katespade.jp
Last fetched
katespade.jp resolves to 2.23.245.60, announced in 2.23.244.0/22 by AKAMAI-AS - Akamai Technologies, Inc. in DE. katespade.jp is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 2.23.245.60
2.23.244.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.197.45.40
23.197.54.0/24 · AKAMAI-AS - Akamai Technologies, Inc. · Edison, US
- 23.209.217.60
23.210.4.0/24 · AKAMAI-AS - Akamai Technologies, Inc. · Taipei, TW
- 23.58.109.62
23.48.12.0/23 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 72.246.28.198
72.246.103.0/24 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 88.221.169.54
88.222.210.0/24 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.52.181.97
23.53.0.0/24 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for katespade.jp is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrant organisation
- stuart weitzman ip,
- Contact emails
- domains@tapestry.com, n_gokyu@katespade.jp, w_takei@katespade.jp
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
Mail and authentication
Nameservers
- a1-1.akam.net
- a11-66.akam.net
- a16-64.akam.net
- a18-65.akam.net
- a26-66.akam.net
- a3-66.akam.net
- dns1.idp365.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
- aspmx4.googlemail.com
- aspmx5.googlemail.com
SPF policy
- include: %{ir}.%{v}.%{d}.spf.has.pphosted.com
Threat-feed evidence
History
Related pages
Pivot from katespade.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: "katespade.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.