Skip to content

Hostname

kayts.ca

Last fetched

kayts.ca resolves to 38.190.133.68, announced in 38.190.133.0/24 by Four-Seasons-Hosting - Four Seasons Hosting LLC in CA. kayts.ca 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 · kayts.caRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/kayts.ca

Resolution chain

IPv6 resolution

No AAAA record for kayts.ca is recorded in WhisperGraph.

Attribution

four seasons

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for kayts.ca. 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
autoconfig.kayts.ca
autodiscover.kayts.ca
chat.kayts.ca
cp2.kayts.ca
mail.kayts.ca
ns1.kayts.ca
ns2.kayts.ca
vccode.kayts.ca
www.kayts.ca

Showing 9 of 9 subdomains (9 per page).

Mail and authentication

Nameservers

  • ns1.kayts.ca
  • ns2.kayts.ca
  • ns-cloud-c1.googledomains.com
  • ns-cloud-c2.googledomains.com
  • ns-cloud-c3.googledomains.com
  • ns-cloud-c4.googledomains.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

  • mail.kayts.ca

SPF policy

  • a: kayts.ca
  • mx: kayts.ca
  • ip: 144.217.195.114
  • ip: 144.217.39.202
  • ip: 144.217.39.247
  • ip: 144.217.58.180
  • ip: 149.56.195.218
  • ip: 192.99.207.74
  • ip: 38.190.133.68

Threat-feed evidence

History

Related pages

Pivot from kayts.ca 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: "kayts.ca"})-[: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.