Skip to content

Hostname

skymark.jp

Last fetched

skymark.jp resolves to 210.169.227.44, announced in 210.169.128.0/17 by ODN - SoftBank Corp. in JP. skymark.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 · skymark.jpRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/skymark.jp

Resolution chain

IPv6 resolution

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

Attribution

softbank

ORIGIN_AS

WHOIS identity

Registrant organisation
skymark airlines
Contact emails
system@skymark.jp

Subdomains

Subdomain
coobee.skymark.jp
ns2.skymark.jp
ns5.skymark.jp
smart.skymark.jp
www.skymark.jp

Showing 5 of 5 subdomains (5 per page).

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

  • ns2.skymark.co.jp
  • ns5.skymark.co.jp
  • dns3.odn.ne.jp
  • ns2.skymark.jp
  • ns5.skymark.jp

MX records

  • mxa-0094d801.gslb.pphosted.com
  • mxb-0094d801.gslb.pphosted.com

SPF policy

  • ip: 61.201.192.128/28
  • ip: 149.72.34.16/32
  • ip: 210.169.227.32/28
  • ip: 124.109.181.7/32
  • ip: 61.208.124.70/32
  • ip: 210.146.26.8/28
  • ip: 210.146.54.96/27
  • ip: 210.169.200.96/28
  • include: _spf.google.com
  • include: _spf.activegate-ss.jp
  • include: spf.ecbeing.co.jp
  • include: spf-bma.mpme.jp
  • include: spf.q-send.jp
  • include: webcas.net
  • ip: 148.163.151.63
  • ip: 148.163.155.7
  • ip: 202.146.20.50
  • ip: 219.94.155.20
  • ip: 219.94.155.22

Threat-feed evidence

History

Related pages

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