TARGET
WAITINGNormalization
Enter a target to start.
NETWORK
DIAGNOSTIC.
Enter a domain or IP. The diagnostic combines public queries and controlled external tests, shows where each piece of evidence comes from and generates local commands to dig into what the browser cannot measure.
01 // TARGET
READYDiagnostic target
ABUSE PROTECTION //
The active port test only runs after the automatic Cloudflare Turnstile validation.
PRIVACY
Private hosts, localhost and .local names are never sent to public services. TLS/HTTP and light TCP checks run on the portal infrastructure; a full Nmap scan stays limited to authorized flows.
DNS
WAITINGPublic resolution
A, AAAA, MX, NS and TXT for domains; PTR for IPv4.
RDAP
WAITINGRegistration and network
Domain registration or the block responsible for the IP.
GEO / ASN
WAITINGPublic IP
Approximate location, ISP and ASN of the first public IPv4 found.
HTTP / HTTPS
WAITINGApplication and HTTPS evidence
HTTP/HTTPS response and observable headers. The runtime exposes neither the peer certificate, the negotiated TLS version nor the cipher; Certificate Transparency data is historical context only.
PORTS / SERVICES
WAITINGExposed services
Quick external test of common ports with service and risk interpretation.
TRACEROUTE
WAITINGRoute and map
Run traceroute on your machine and paste the output here, or compare with the route seen from probes on other networks.
RESULT // VERDICT
Operational verdict
02 // COMMAND PACK
Generated commands
Run a diagnostic to generate the commands.
Recommended sequence
1DNSFind the address and check the published records.
2RDAP / ASNIdentify the registration, organization and responsible network.
3HTTP / HTTPSObserve the response, redirects and headers; check the peer certificate, protocol and cipher locally when needed.
4PORTSConfirm the expected service is reachable.
5NMAPIdentify services only when you need to dig deeper.
6TRACEROUTEAnalyze the path and see the hops on the map.
RESULT // WORKFLOWUse the result in your ticket or handoff
History stays in this browser.RECENT LOCAL QUERIES
Frequently asked questions
What does Network Diagnostic check?
For a domain or IP, it queries DNS, RDAP and ASN, tests the HTTP and HTTPS response, checks common ports and prepares the traceroute. Each block shows where the evidence came from and what still needs to be confirmed on your network.
Why is the result different from what I see on my computer?
The external tests run from the Bit Happens infrastructure, not from your network. A firewall, VPN, local DNS or CGNAT can make the same target answer differently for you. Use the suggested commands to compare.
Does an HTTPS timeout mean an invalid certificate?
No. A timeout means the connection did not complete in time, because of a firewall block, a service down on port 443 or the wrong hostname. A certificate problem shows up as a TLS error, not as a timeout.
Can I diagnose an IP or host on my internal network?
Not through the portal. Private addresses, localhost and .local names are never sent to external services. For them, run locally the commands the diagnostic generates.
Is the port test safe for the target?
It only tries to open a TCP connection on a few common ports, without reading banners or trying to authenticate. Even so, use it only on assets you manage or are authorized to test.