HTTPS & connectivity
Secure connections, redirects and visible configuration.
A LITTLE CLARITY FOR YOUR WEBSITE
Is my website
broken?
Spot obvious website problems. Understand what to fix. See the evidence behind every finding.
Your website snapshot
Fictional example. No website was contacted.
Inspect sampled requests
This is a limited public sample, not a security audit. “Looks OK” means no supported pattern was found in the sampled responses. It does not mean the whole site is safe.
Four checks. No guesswork dressed up as certainty.
WordPress hygiene
Demo content, visible shortcodes and directory listings.
Possible exposed secrets
Credential-like patterns, always masked. Never tested.
Production placeholders
Lorem ipsum and unfinished template text.
What happens to my URL?
When you request a check, your URL is sent to Arcdrake’s scanner. It fetches at most six public responses, including redirects, an HTTP variant and up to two linked first-party JS/CSS files. Target websites see the scanner’s requests and outgoing IP address. Inputs and redacted results are processed in memory; they are not deliberately saved. For abuse protection, the scanner keeps a daily pseudonymous client key and target hostname for up to two minutes. Hosting providers process connection data separately. Do not submit private or signed links. Optional usage counts are separate and never include your URL or results.
Public hostnames on standard HTTP/HTTPS ports only; numeric IP URLs are not supported. At most six responses of 256 KiB each and 25 seconds per scan. JavaScript is not executed. Login pages, challenges, compression and unusual encodings can make results inconclusive. Certificate expiry and certificate-chain details are not checked. The shared allowance is 100 attempts per UTC day; capacity is not guaranteed.