Skip to content

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)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · skyticket.jpRouting diversity1.5/10Peering density4.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.6/10canon.whisper.security/host/skyticket.jp

Resolution chain

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

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.