Exposed files: .git, .env and backups in the web root
An agency uploaded the whole project folder. You find the repository, the credentials and a database dump, block them in nginx and keep Let's Encrypt working.
WebBeginner 20 min Simulation in your browser, no real systems
You can check your own site with curl for exposed files such as /.git/HEAD, /.env and database dumps.
You can block such files in nginx with location rules and know why /.well-known/ needs an exception.
You know that blocking alone is not enough: exposed credentials get replaced, and the way files reach the server gets changed.