Skip to content

Hostname

cn.yazaki.com

Last fetched

cn.yazaki.com resolves to 202.134.62.179, announced in 202.134.62.0/24 by AZURANCELIMITED-AS-AP - Azurance Limited in HK. cn.yazaki.com 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 · cn.yazaki.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/cn.yazaki.com

Resolution chain

IPv6 resolution

No AAAA record for cn.yazaki.com is recorded in WhisperGraph.

Attribution

azurance

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cn.yazaki.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
lyncdiscover.cn.yazaki.com
mail.cn.yazaki.com
meet.cn.yazaki.com
sip.cn.yazaki.com
sipexternal.cn.yazaki.com

Showing 5 of 5 subdomains (5 per page).

Mail and authentication

Nameservers

  • ns1-07.azure-dns.com
  • ns4-07.azure-dns.info
  • ns2-07.azure-dns.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
  • ns3-07.azure-dns.org

MX records

  • cn-yazaki-com.mail.protection.outlook.com

SPF policy

  • ip: 58.48.28.10/30
  • ip: 122.5.16.114/30
  • ip: 58.34.65.114/30
  • ip: 119.145.137.122/30
  • ip: 117.14.60.130/30
  • ip: 222.223.54.138/30
  • ip: 221.239.110.146/30
  • ip: 121.11.25.154/30
  • ip: 211.95.28.162/30
  • ip: 120.87.93.163/30
  • ip: 112.64.136.18/30
  • ip: 222.212.93.180/30
  • ip: 219.128.140.194/30
  • ip: 221.5.8.2/30
  • ip: 121.11.27.202/30
  • ip: 221.4.173.210/30
  • ip: 221.239.110.218/30
  • ip: 219.138.199.226/30
  • ip: 119.36.187.23/30
  • ip: 221.214.215.23/30
  • ip: 58.34.141.234/30
  • ip: 218.16.179.242/30
  • ip: 116.142.72.250/30
  • ip: 58.248.3.4/30
  • ip: 221.5.4.50/30
  • ip: 222.71.104.66/30
  • ip: 58.23.112.66/30
  • ip: 101.74.214.66/30
  • ip: 123.157.217.74/30
  • ip: 218.66.254.82/30
  • ip: 106.41.49.82/30
  • ip: 115.236.0.90/30
  • ip: 112.195.202.94/30
  • include: azurance.com
  • include: _spf.psm.knowbe4.com
  • include: spf.protection.outlook.com
  • ip: 106.186.192.47
  • ip: 123.206.106.225
  • ip: 139.138.32.50
  • ip: 139.138.32.51
  • ip: 139.138.32.52
  • ip: 139.138.32.61
  • ip: 139.138.32.86
  • ip: 165.1.245.76
  • ip: 216.71.138.147
  • ip: 216.71.138.148
  • ip: 216.71.138.156
  • ip: 216.71.138.158
  • ip: 216.71.138.203
  • ip: 61.169.17.42

Threat-feed evidence

History

Related pages

Pivot from cn.yazaki.com 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: "cn.yazaki.com"})-[: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.