Skip to content

general_enum: Yandex branch should call scrape_yandex, not scrape_bing#515

Open
ChrisJr404 wants to merge 1 commit into
darkoperator:masterfrom
ChrisJr404:fix-yandex-uses-bing-505
Open

general_enum: Yandex branch should call scrape_yandex, not scrape_bing#515
ChrisJr404 wants to merge 1 commit into
darkoperator:masterfrom
ChrisJr404:fix-yandex-uses-bing-505

Conversation

@ChrisJr404
Copy link
Copy Markdown

Closes #505.

The Yandex branch in general_enum invoked scrape_bing(domain), so selecting -y (or whichever flag enables do_yandex) silently ran a second Bing scrape and labeled the results as Yandex. The Bing branch above and the existing call at cli.py:2195 already use scrape_yandex correctly — this is just a copy-paste from the Bing branch immediately above.

Diff

One token change in dnsrecon/cli.py:

-            yandex_rcd = se_result_process(res, domain, scrape_bing(domain))
+            yandex_rcd = se_result_process(res, domain, scrape_yandex(domain))

Verification

$ python3 -m pytest tests/
============================= 53 passed in 12.13s ==============================

The Yandex branch in general_enum invoked scrape_bing(domain), so
selecting -y (or whichever flag enables do_yandex) silently ran a
second Bing scrape and labeled the results as Yandex. The Bing branch
above and the call site at line 2195 already use scrape_yandex
correctly, so this is just a copy-paste bug.

Closes darkoperator#505
@t0kubetsu
Copy link
Copy Markdown
Contributor

t0kubetsu commented May 5, 2026

Hi @ChrisJr404, just a heads-up — I already have an open PR covering this Yandex scraper fix (along with the dead 'address' guard) at #507. Happy to coordinate or defer if it helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

general_enum: Yandex branch calls scrape_bing() instead of scrape_yandex()

2 participants