Hostname
skyticket.jp
Last fetched
skyticket.jp resolves to 104.102.60.10, announced in 104.102.32.0/19 by AKAMAI-AS - Akamai Technologies, Inc. in DE. skyticket.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
- 104.102.60.10
104.102.32.0/19 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.197.140.7
23.197.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.197.143.155
23.197.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.4.45.18
23.4.32.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Atlanta, US
- 23.60.120.174
23.60.112.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Chicago, US
- 23.63.129.108
23.63.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
IPv6 resolution
No AAAA record for skyticket.jp is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrant organisation
- adventure.,inc.
- Contact emails
- domain-master@adventure-inc.co.jp, staff-all@adventure-inc.co.jp, system@adventure-inc.co.jp
Subdomains
Showing 12 of 70. 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
Mail and authentication
Nameservers
- a1-173.akam.net
- a12-64.akam.net
- a13-65.akam.net
- a14-66.akam.net
- a6-67.akam.net
- a7-64.akam.net
- 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
MX records
- mx.skyticket.com
SPF policy
- ip: 182.48.35.133/32
- ip: 59.106.226.52/32
- include: devmail01.spf.skyticket.jp
- include: spf.te.smtps.jp
- ip: 49.212.99.181
Threat-feed evidence
History
Related pages
Pivot from skyticket.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: "skyticket.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.