Domain Checker

Execution mode changes what can be observed

Client mode is conservative because CORS can hide HTTP status information. DNS queries are sent to the selected browser-accessible DNS-over-HTTPS resolver.

01 · Targets

Domain input

Import TXT / CSV

One domain or URL per line

Paste one domain per line or import a TXT/CSV file.

02 · Controls

Scan options

Execution Client-side only DNS Automatic HTTPS Enabled Performance 10 jobs · 5s · 1 retry

Execution

Choose where network checks run.

Execution mode GitHub Pages works independently in client mode.

DNS resolver

Override the resolver used for this scan.

Resolver Traditional UDP, TCP or DoT DNS requires hybrid or server mode.

Not tested

Performance

Bound concurrency, timeout and retry behaviour.

Concurrency Simultaneous domain jobs Timeout (ms) Per DNS, HTTPS or backend operation Retries Transient failures only Start delay (ms) Delay between new jobs

Network checks HTTPS probe Browser best-effort or backend-readable, depending on mode Allow opaque browser fallback Available only when HTTPS runs in the browser

03 · Progress

Scan lifecycle

Idle

No scan started

Total results 0

HTTPS readable 0

HTTPS opaque 0

DNS only 0

Issues / skipped 0

04 · Results

Domain results

0 shown of 0

DNS and HTTPS results for submitted domains
										Details

Status guide

How to interpret results

Client: DNS and HTTPS run in the browser; CORS may hide HTTP details.
Hybrid: DNS normally runs in the browser while HTTPS runs through the configured backend.
Server: DNS and HTTPS are delegated to the configured backend API.
Resolver provenance: Each result records the resolver identity, transport and execution source.