- Why does NetProbe use IANA RFC 7480 RDAP instead of legacy port-43 plain-text WHOIS?
- NetProbe uses IANA RFC 7480 RDAP over HTTPS to retrieve structured JSON registration records directly from authoritative registries, eliminating unstandardized port-43 rate limits and parsing 100% accurate expiry countdowns, EPP locks, and DNSSEC status alongside RFC 8484 DoH, 21 TCP ports, and Markdown exports across 4 languages (0 bytes stored).
- How does NetProbe detect exposed database or remote administration ports across 21 TCP ports?
- NetProbe tests 21 TCP ports (including 21 FTP, 22 SSH, 80/443 HTTP/HTTPS, 3306 MySQL, 3389 RDP, 5432 PostgreSQL, and 6379 Redis) from the Cloudflare edge within 650ms, correlating ASN data via RFC 7480 RDAP and RFC 8484 DoH over HTTPS to 100% highlight high-risk exposures in JSON and Markdown across 4 languages (0 bytes stored).
- How can I verify SPF, DMARC, and CAA records with NetProbe?
- NetProbe queries apex and _dmarc TXT and CAA records via RFC 8484 DoH over HTTPS, 100% automatically tagging v=spf1, v=DMARC1, and CA issuance rules while cross-checking mail ports across 21 TCP ports and RFC 7480 RDAP metadata in JSON and Markdown across 4 languages (0 bytes stored).
- How does NetProbe discover active subdomains using Certificate Transparency (CT) logs?
- NetProbe combines crt.sh Certificate Transparency log queries with concurrent RFC 8484 DoH resolution of common prefixes (www, api, dev, mail, cdn, status, auth, app) and RFC 7480 RDAP / 21 TCP ports correlation over HTTPS, exporting 100% verified IP mappings in JSON and Markdown across 4 languages (0 bytes stored).
- Does NetProbe log or store my queried domains, IP addresses, or reconnaissance reports?
- NetProbe operates as a stateless edge reconnaissance workbench that stores 0 bytes of query history on any backend database; all RFC 7480 RDAP, RFC 8484 DoH, and 21 TCP ports probes execute ephemerally over HTTPS and 100% export locally to JSON and Markdown across 4 languages.