Skip to content

Hostname

cpskyhawks.com

Last fetched

cpskyhawks.com resolves to 23.193.114.50, announced in 23.193.114.0/24 by AKAMAI-ASN1 - Akamai International B.V. in IN. cpskyhawks.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 · cpskyhawks.comRouting diversity1.5/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/cpskyhawks.com

Resolution chain

IPv6 resolution

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

Attribution

akamai international

ORIGIN_AS

WHOIS identity

Registrar
iana:3786
Registrant organisation
domain admin
Contact emails
cpskyhawks.com@domainsbyproxy.com, internicadmin@nba.com

Subdomains

Subdomain
www.cpskyhawks.com

Showing 1 of 1 subdomain (1 per page).

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

Mail and authentication

Nameservers

  • a1-148.akam.net
  • a12-65.akam.net
  • a16-64.akam.net
  • a18-65.akam.net
  • a5-65.akam.net
  • a7-67.akam.net
  • 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

  • cpskyhawks-com.mail.protection.outlook.com

SPF policy

  • ip: 50.204.228.17/32
  • ip: 50.204.228.5/32
  • a: cpskyhawks.com
  • mx: cpskyhawks.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com

Threat-feed evidence

History

Related pages

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