Skip to content

Hostname

kenzz.com

Last fetched

kenzz.com resolves to 13.225.245.116, announced in 13.225.240.0/21 by AMAZON-02 - Amazon.com, Inc. in PT. kenzz.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 · kenzz.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/kenzz.com

Resolution chain

IPv6 resolution

No AAAA record for kenzz.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of kenzz.com owner
Contact emails
k01064851888@hotmail.com, lawyer247@hotmail.com, zeu@dreamwiz.com, 3b6d9faa-68ee-4b65-9e5d-eff42d9f7731@identity-protect.org, 6e2cc248-5e57-4596-ab1d-51c65e078168@identity-protect.org, a02460b9-bb95-4b05-a706-f4bad16d7d3a@identity-protect.org, ac6c148b-8c6d-4019-8439-5f168d4cd70d@identity-protect.org, dd353690-ca6a-476b-a515-1146764ee515@identity-protect.org, ee3f4f45-b0bc-4395-a4b9-b0ee89c07d26@identity-protect.org

Subdomains

Subdomain
airbyte.kenzz.com
assets.kenzz.com
bosla.kenzz.com
www.kenzz.com

Showing 4 of 6. 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

  • ns-413.awsdns-51.com
  • ns-985.awsdns-59.net
  • ns-1448.awsdns-53.org
  • ns-1783.awsdns-30.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • ms98638444.msv1.invalid

SPF policy

  • include: _spf.google.com
  • include: transmail.net

Threat-feed evidence

History

Related pages

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