Skip to content

Hostname

nextage.jp

Last fetched

nextage.jp resolves to 13.230.63.16, announced in 13.230.0.0/15 by AMAZON-02 - Amazon.com, Inc. in JP. nextage.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 · nextage.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint4.0/10canon.whisper.security/host/nextage.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
nextage co,ltd
Contact emails
admin@nextage.jp

Subdomains

Subdomain
ap.nextage.jp
api.nextage.jp
apl.nextage.jp
cdn.nextage.jp
dorakuru-stg.nextage.jp
dorakuru.nextage.jp
f-lbweb-w-test.nextage.jp
img.nextage.jp
ir.nextage.jp
mail.nextage.jp
my-deltoenmpev.nextage.jp
my-satnigg.nextage.jp

Showing 12 of 34. 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

  • ns2.dc.ctc.ad.jp
  • ns1.hs.ctc.jp
  • ns3.ctc.jp

MX records

  • nextage-jp.mail.protection.outlook.com

SPF policy

  • ip: 54.192.0.0/10
  • ip: 18.176.0.0/13
  • ip: 13.112.0.0/14
  • ip: 52.196.0.0/14
  • ip: 52.68.0.0/15
  • ip: 13.230.0.0/16
  • ip: 54.95.0.0/16
  • ip: 54.168.208.0/20
  • include: spf.protection.outlook.com
  • include: _spf.websolve.com
  • include: kfs.kddi.ne.jp
  • include: zcsend.net
  • ip: 113.40.182.130
  • ip: 149.72.77.72
  • ip: 193.115.146.191
  • ip: 223.29.12.182
  • ip: 223.29.33.6
  • ip: 3.114.18.161
  • ip: 54.248.126.153
  • ip: 54.64.25.50

Threat-feed evidence

History

Related pages

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