Skip to content

Hostname

hkp.com

Last fetched

hkp.com resolves to 83.149.101.233, announced in 83.149.64.0/18 by LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. in NL. hkp.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 · hkp.comRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.8/10canon.whisper.security/host/hkp.com

Resolution chain

IPv6 resolution

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

Attribution

leaseweb netherlands

ORIGIN_AS

WHOIS identity

Registrar
iana:1408
Registrant organisation
ernst van der linden
Contact emails
ernst.vanderlinden@hkp.com, noreply@data-protected.net

Subdomains

Subdomain
adfs.hkp.com
autodiscover.hkp.com
hostmaster.hkp.com
link.hkp.com
mail.hkp.com
mi.hkp.com
sentry.hkp.com
wildcard.hkp.com
www.hkp.com
xcxj.hkp.com

Showing 10 of 13. 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

  • ns01.mmc.com
  • ns02.mmc.com
  • ns03.mmc.com
  • ns04.mmc.com
  • ns05.mmc.com
  • usash15-02dns01.mrshmc.com
  • usdal1-03dns01.mrshmc.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

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

SPF policy

  • include: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email

Threat-feed evidence

History

Related pages

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