The tool requires DNS TXT verification before an allowed check can run. Invalid proof or an unsupported target stops the process.
- DNS TXT proof
- Ownership validation
- Permitted checks
How to use this tool
- Enter the unproxied public server hostname and confirm your authorization.
- Create the verification record and publish the exact TXT name and value with your DNS provider.
- After the record is visible, verify DNS and run the allowed port check before the proof expires.
Understanding the results
- Ownership proof
- The temporary record binds verification to the exact hostname. Creating the record instructions does not initiate port connections.
- Reachability
- An open result indicates a TCP connection succeeded from this server at that moment. It does not establish which application is running or whether it is vulnerable.
- Unreachable ports
- A failed connection can reflect filtering, routing or no listener. It is not a complete diagnosis of the remote service.
What this check covers
The checker supports only TCP 22, 25, 80, 443, 587, 3306, 3389, 5432, 8080 and 8443 on one public address. It excludes private networks and shared Cloudflare edge addresses. Do not use other shared or CDN hosts. It does not scan custom ranges, UDP or credentials.
Common questions
Why is the check button initially disabled?
Create the hostname verification instructions first. The server still requires the matching published DNS proof before it permits any port connections.
What if the TXT record cannot be found?
Check its name and value, allow DNS caches to update and retry before the thirty-minute proof expires. Missing proof never authorizes a scan.