fix(enrichers): dnsx stdin input + configurable Scamalytics API host

[Topman3579]

Two enrichers return an empty result instead of failing loudly, so the task is reported as succeeded and nothing shows up in the graph.

1. domain_to_dns — dnsx no longer accepts a bare -d

DnsxTool.resolve_domain() builds:

dnsx -d <domain> -a -aaaa -json -silent

Since dnsx 1.2, -d means "bruteforce this domain" and requires a wordlist:

$ docker run --rm projectdiscovery/dnsx -d example.com -a -aaaa -json -silent
[FTL] missing wordlist(w) flag required with domain(d) input
$ echo $?
0

The exit code is 0, so nothing raises — the enricher just returns [] and Celery logs succeeded. From the UI it looks like the domain simply has no DNS records.

Fix: feed the single target on stdin, which is the supported single-target invocation:

sh -c "echo <domain> | dnsx -a -aaaa -json -silent"

DockerTool.launch() gains an optional entrypoint argument so a shell can be placed in front of the image entrypoint. The domain is passed through shlex.quote().

Verified against projectdiscovery/dnsx:latest (v1.2.2):

resolve_domain("<a test domain>") -> ['13.227.138.65', '13.227.138.39', '13.227.138.34', '13.227.138.124']

2. ip_to_fraudscore — Scamalytics API host is per-account

The host is hardcoded:

requests.get(f'https://api12.scamalytics.com/v3/{api_username}/?key={api_key}&ip={ip.address}')

Scamalytics provisions each account on a numbered API node and hands out the full base URL at signup. An account on a different node gets a plain 404 from api12, with the same silent-empty-result outcome. On a live v3 account provisioned on api11:

host	result
the account's own node	200 + full JSON
api12	404 Not Found

Fix: read the host from a SCAMLYTICS_API_HOST secret / env var, defaulting to api12 so existing deployments are unchanged.

Notes

• No behaviour change for anyone already working: the Scamalytics default is preserved, and the dnsx change only alters how the single target is passed.
• Happy to split this into two PRs, add tests, or make the dnsx change use a different mechanism if you prefer — just say the word.

[dextmorgn]

This looks great @Topman3579, thanks !