I tried to visit Www.severedbytesnet, but the site is not loading right and I’m not sure if it’s down, broken, or moved. I need help figuring out what happened and how to access the website again.
Sounds like the domain might be typed wrong first off. ‘Www.severedbytesnet’ is missing the dot, so try severedbytes.net or www.severedbytes.net.
If you still get errors, check a few things fast:
- Run it on Down For Everyone Or Just Me.
- Check WHOIS for severedbytes.net and see if the domain expired.
- Try the Wayback Machine. If the site moved or died, old snapshots might show links or contact info.
- Flush your DNS, or try another network. Sometimes your ISP cache gets wonky.
- Check the site on your phone with Wi-Fi off. Easy test.
If the domain is gone, it was either not renewed, parked, or moved. If WHOIS shows a new registrar or status like redemptionPeriod, that tells you a lot. If you want, post the exact error msg and people here can narrow it down faster.
First thing, that address as written is basically not a real web address. Www.severedbytesnet has no dot before net, so a browser can choke on it or turn it into a search instead of a site. I’d try severedbytes.net directly in the address bar, not Google, because browsers love being ‘helpful’ in the most annoyng way possible.
I slightly disagree with @voyageurdubois on one point: if it’s ‘not loading right,’ it may not be fully down at all. Sometimes the domain resolves, but the site assets are broken because of expired SSL, mixed content, bad redirects, or a half-migrated host. Open the browser console if you can and look for stuff like:
- certificate/privacy error
- too many redirects
- 403 / 404 / 500 errors
- missing CSS/JS files
- Cloudflare or host error page
Also try a different browser in private mode. Extensions, old cookies, and cached redirects can mess things up more than people think. If the homepage is busted, test a deeper path like /about or /contact if you know one. That can tell you whether the whole site died or just the front page did.
If you post the exact error text, people can probly narrow it down in like 2 replies.
I’d check the domain itself, not just the page behavior. Sometimes a site “looks broken” because the registration expired, nameservers changed, or DNS is propagating badly after a move. @voyageurdubois is right to question the typed address, but I wouldn’t assume it is only a typo issue.
What to do next:
- Run a WHOIS lookup and see if the domain is still registered.
- Check DNS records with a DNS checker. If A/AAAA records are missing, the site will not resolve correctly.
- Test from another network, like mobile data. That rules out ISP or local DNS issues.
- Flush local DNS cache and switch to a public resolver like Cloudflare or Google DNS.
- Search web cache or the Internet Archive to see whether the site was moved or renamed.
If it was recently migrated, recovery can take a while.
Pros for the ‘’: helps readability if you organize error details before posting.
Cons for the ‘’: not really relevant unless you are documenting the issue for others.
If you can share whether you get NXDOMAIN, timeout, or a parked-page result, that narrows it fast.