> For the complete documentation index, see [llms.txt](https://www.webhackingtips.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.webhackingtips.com/weekly-tips/week-17-gobuster-tips.md).

# Week 17 - GoBuster Tips

## GoBuster: Enumeration Tips

It’s week 17 of the Web Hacking Series, and it’s on a Tuesday cause May is off to a busy start over at [Echelon Risk + Cyber](https://www.linkedin.com/company/echelon-risk-cyber/)!\
&#x20;\
If you are involved in app sec, you probably have a preference between DirBuster vs. GoBuster vs. Dirb. My personal preference (and the correct answer :p) is GoBuster!\
&#x20;\
One of my favorite things about GoBuster is how you can refine the scanning options. Here are some I find most useful:

* -s "204,301,302,307,401,403" ==> Only show results with these status codes
* -b "302" ==> Exclude 302 status codes
* \--exclude-length 3571 ==> Exclude server responses of length 3571
* -k ==> Disable HTTPS verification\
  &#x20;

The –exclude-length is particularly useful for dealing with a 404 error that appears to be a legitimate (200 OK) page. Know any other GoBuster tips & tricks? Share them in the comments below.

![](/files/1iUBNjewqTp9XNY292PC)
