Skip to content

Hostname

keekass.com

Last fetched

keekass.com resolves to 88.208.36.13, announced in 88.208.32.0/20 by ADVANCEDHOSTERS-AS - DataWeb Global Group B.V. in NL. keekass.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 · keekass.comRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/keekass.com

Resolution chain

IPv6 resolution

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

Attribution

dataweb global group

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
domain admin
Contact emails
admin@domainregistriesfoundation.com, 3be2727e1660439b9aa2c78b9a854280.protect@whoisguard.com, 6653736d2792441dbc170076ac875a8b.protect@withheldforprivacy.com

Subdomains

Subdomain
mail.keekass.com
mail2.keekass.com
vcdn.keekass.com
vcdn1.keekass.com
www.keekass.com

Showing 5 of 7. 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.pub-ns.me
  • ns2.pub-ns.me
  • 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.keekass.com
  • mail2.keekass.com

SPF policy

  • include: _spf.smtp.advancedhosters.com
  • a: keekass.com

Threat-feed evidence

History

Related pages

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