Skip to content

Hostname

yahoo.co.nz

Last fetched

yahoo.co.nz resolves to 13.248.158.7, announced in 13.248.144.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. yahoo.co.nz 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 · yahoo.co.nzRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/yahoo.co.nz

Resolution chain

IPv6 resolution

No AAAA record for yahoo.co.nz is recorded in WhisperGraph.

Attribution

Aws

cloud · MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:markmonitor. inc
Registrant organisation
yahoo!
Contact emails
domainadmin@yahoo-inc.com

Subdomains

Subdomain
_cisco-uds.yahoo.co.nz
_collab-edge.yahoo.co.nz
_cuplogin.yahoo.co.nz
_etcd-server-ssl.yahoo.co.nz
_mta-sts.yahoo.co.nz
_tls.yahoo.co.nz
a.yahoo.co.nz
abby_shep.yahoo.co.nz
acapi.yahoo.co.nz
admin.yahoo.co.nz
akamai-test-origin.yahoo.co.nz
akamai-test.yahoo.co.nz

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

  • hidden-master.yahoo.com
  • ns1.yahoo.com
  • ns3.yahoo.com
  • ns4.yahoo.com
  • ns5.yahoo.com
  • 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

  • mta5.am0.yahoodns.net
  • mta6.am0.yahoodns.net
  • mta7.am0.yahoodns.net

SPF policy

  • redirect: _spf.mail.yahoo.com

Threat-feed evidence

History

Related pages

Pivot from yahoo.co.nz 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: "yahoo.co.nz"})-[: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.