Redirect 80 → 443
- Input
- return 301 https://$host$request_uri;
- Expected output
- Migração para HTTPS
Common nginx case.
port 80
Port 80 is still relevant for plain HTTP, redirects to HTTPS and some controlled internal environments.
Common nginx case.
Depends on context and policy.
Deliberate decision: unauthorized port scanning is an abuse vector and has legal implications in several countries. We prefer a clear, safe reference.
The issue is the protocol without TLS, not the port number itself.
For many sites yes, at least to redirect users and validate certain flows.
Cleartext HTTP. In production always use HTTPS (443).
Everything runs locally in your browser from an embedded catalog. This tool does not connect to IPs or ports, it is not a scanner.