Skip to content

Hostname

ing-host.jp

Last fetched

ing-host.jp resolves to 210.175.228.15, announced in 210.175.224.0/20 by FRT - FRT Inc. in JP. ing-host.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 · ing-host.jpRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/ing-host.jp

Resolution chain

IPv6 resolution

No AAAA record for ing-host.jp is recorded in WhisperGraph.

Attribution

first riding

ORIGIN_AS

WHOIS identity

Registrant organisation
ing inter-media
Contact emails
e-info@21-domain.com

Subdomains

Subdomain
abasa.ing-host.jp
bitaro14.ing-host.jp
bitaro21.ing-host.jp
dns0.ing-host.jp
dns1.ing-host.jp
dns2.ing-host.jp
dns3.ing-host.jp
genki.ing-host.jp
gurukun.ing-host.jp
gurukun44.ing-host.jp
irabucha13.ing-host.jp
mail.ing-host.jp

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

  • dns1.ing-host.jp
  • dns2.ing-host.jp
  • dns3.ing-host.jp
  • 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

  • mail.ing-host.jp
  • www.ing-host.jp

SPF policy

  • ip: 61.195.190.0/24
  • ip: 210.175.228.0/24
  • include: aspmx.googlemail.com
  • include: spf.tricorn.net

Threat-feed evidence

History

Related pages

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