Skip to content

Hostname

kfc.tt

Last fetched

kfc.tt resolves to 100.28.44.77, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. kfc.tt 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 · kfc.ttRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/kfc.tt

Resolution chain

IPv6 resolution

No AAAA record for kfc.tt is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for kfc.tt. 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
backtoschool.kfc.tt
com.kfc.tt
deliveryadmin.kfc.tt
kfctt-bncprd.kfc.tt
kfctt-bncuat.kfc.tt
mail.kfc.tt
order.kfc.tt
promotions.kfc.tt
rcpt.kfc.tt
sso.kfc.tt
updates.kfc.tt
www.kfc.tt

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

  • katelyn.ns.cloudflare.com
  • peyton.ns.cloudflare.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

  • kfc-tt.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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