Skip to content

Hostname

tp1.jp

Last fetched

tp1.jp resolves to 122.152.0.81, announced in 122.152.0.0/20 by FBDC - FreeBit Co.,Ltd. in JP. tp1.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 · tp1.jpRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/tp1.jp

Resolution chain

IPv6 resolution

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

Attribution

freebit

ORIGIN_AS

WHOIS identity

Registrant organisation
hi-bit co.,ltd.
Contact emails
contents_planning_hiho@po.hikari.co.jp, itlab-web-order@po.hikari.co.jp, tadanori_ito@po.hikari.co.jp

Subdomains

Subdomain
entry-authori.tp1.jp
entry-em.tp1.jp
entry-isp.tp1.jp
entry-t.tp1.jp
entry-tab.tp1.jp
entry-type-d.tp1.jp
entry.tp1.jp
gm.tp1.jp
hb.tp1.jp
mail.tp1.jp
point.tp1.jp
ssl.tp1.jp

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

  • ns1.freebit.net
  • ns2.freebit.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

  • hbj0.mx.cloud-mail.jp
  • hbj0.mx2.cloud-mail.jp

SPF policy

  • a: hbj0.spf.cloud-mail.jp

Threat-feed evidence

History

Related pages

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