Skip to content

Hostname

kpc.com.kw

Last fetched

kpc.com.kw resolves to 52.166.12.48, announced in 52.160.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. kpc.com.kw 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 · kpc.com.kwRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint6.0/10canon.whisper.security/host/kpc.com.kw

Resolution chain

IPv6 resolution

No AAAA record for kpc.com.kw is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for kpc.com.kw. 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
adfs.kpc.com.kw
apply.kpc.com.kw
apps1.kpc.com.kw
cbkforms.kpc.com.kw
cbwan.kpc.com.kw
coesm.kpc.com.kw
corporateblob.kpc.com.kw
cup.kpc.com.kw
cvwc.kpc.com.kw
dvg-s.kpc.com.kw
eapp.kpc.com.kw
emtaz.kpc.com.kw

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

  • ns1-01.azure-dns.com
  • ns4-01.azure-dns.info
  • ns2.kpc.com.kw
  • ns3.kpc.com.kw
  • ns4.kpc.com.kw
  • ns2-01.azure-dns.net
  • ns3-01.azure-dns.org

MX records

  • mxa-001d7301.gslb.pphosted.com
  • mxb-001d7301.gslb.pphosted.com

SPF policy

  • ip: 195.88.222.15/32
  • ip: 195.88.222.16/32
  • ip: 195.88.223.68/32
  • include: spf.protection.outlook.com
  • include: spf-001d7301.pphosted.com
  • mx: kpc.com.kw

Threat-feed evidence

History

Related pages

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