Skip to content

Hostname

jtp.co.jp

Last fetched

jtp.co.jp appears in WhisperGraph with partial WHOIS records but no current public IPv4 resolution.

Nutrition Label

WHISPER CANON · jtp.co.jpRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/jtp.co.jp

Resolution chain

jtp.co.jp has no current public IPv4 resolution in WhisperGraph. The WHOIS record below is the only graph data we have on this hostname.

WHOIS identity

Registrar
Organization
japan third party co.,ltd.
Contact emails

Subdomains

18 observed subdomains of jtp.co.jp.

Web-graph footprint

Distinct hostnames that link to or from jtp.co.jp in the public web crawl.

129 sites link to this hostname.

31 sites linked to from this hostname.

Threat posture

History

Mail and authentication

SPF policy

42 SPF mechanisms authorising senders for jtp.co.jp.

MechanismTarget
SPF_Ab.spf.service-now.com
SPF_Ac.spf.service-now.com
SPF_Ad.spf.service-now.com
SPF_Amail.lw-cloud.jp
SPF_INCLUDEspf.mta.hdems.com
SPF_INCLUDEspf.protection.outlook.com
SPF_IP101.97.26.0/24
SPF_IP118.67.107.0/24
SPF_IP158.201.240.7
SPF_IP158.201.242.128/25
SPF_IP160.16.125.241/32
SPF_IP160.86.241.170
SPF_IP182.169.51.138
SPF_IP182.236.75.0/24
SPF_IP182.236.82.0/23
SPF_IP194.223.158.110/31
SPF_IP194.223.158.112/29
SPF_IP202.143.90.187/32
SPF_IP202.218.104.65
SPF_IP202.218.104.66/31
SPF_IP202.218.104.7
SPF_IP202.218.104.8
SPF_IP202.222.24.192/26
SPF_IP202.230.170.144/28
SPF_IP202.234.6.233
SPF_IP202.234.6.241
SPF_IP202.239.55.0/25
SPF_IP203.167.59.32/27
SPF_IP210.152.142.159/26
SPF_IP210.152.142.160/28
SPF_IP210.152.142.176/31
SPF_IP210.152.142.178
SPF_IP210.152.202.128/27
SPF_IP210.152.41.176/28
SPF_IP210.171.14.0/24
SPF_IP210.171.15.2/32
SPF_IP39.110.200.74
SPF_IP42.125.251.0/24
SPF_IP54.248.123.160/32
SPF_IP59.106.90.64/26
SPF_IP61.125.131.252
SPF_IP61.125.131.253

Related pages

Pivot deeper into the graph from jtp.co.jp.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "jtp.co.jp"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

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