Domain Change

[SiongokBrian]

I used zoomeye.hk whe zoomeye.com became unavailable.

I also used zoomeye.hk as SSO. Should I remove it as zoomeye.org looks to be running after some long pause and was zoomeye.hk a legit zoomeye domain?

[dogancanbakir]

ZoomEye recently updated its domain, and we have implemented the new API. You can find it at this link: https://github.com/projectdiscovery/uncover/blob/main/sources/agent/zoomeye/zoomeye.go#L15. It's included in the latest version.

[bad-antics]

Good catch. ZoomEye has gone through a few domain changes:

• zoomeye.com — original domain, was down for a period
• zoomeye.hk — temporary alternative that appeared during the .com downtime
• zoomeye.org — appears to be the current active domain

Regarding zoomeye.hk:
It was used as a mirror/alternative during the .com outage. Whether it was officially operated by Knownsec (ZoomEye's parent company) is unclear, but it did function as a working ZoomEye instance. If you created an account via SSO on .hk, your credentials may or may not carry over to .org.

What to do:

1. Update uncover config to use the current working domain:

# ~/.config/uncover/provider-config.yaml
zoomeye:
  - YOUR_API_KEY  # get new key from zoomeye.org

2. Check if your existing API key works against zoomeye.org — if not, register a new account there

3. For uncover itself, the domain should be handled in the source code. You could check if there's been an update:

uncover -update

If zoomeye.org is working now, the uncover team should update the hardcoded endpoint. Worth opening a PR or issue if it hasn't been updated yet.