SITE UNDER CONSTRUCTION. Everything here is provided AS IS, WITHOUT WARRANTIES, to the extent the law allows. It is information, not professional advice. Use at your own risk. Terms and liability limits →

eThorns ES
Menu
Buy us a coffeeEspañoleThorns 2026 · Made in Colombia
← DNS, email & networkES

Tool 2.8

Is it down? Check if a website is up, and how fast

Check whether a website answers, with its HTTP status, response time, redirects and HTTPS, measured once from our server in Colombia.

Online checkThe address goes to our server (api.ethorns.com), which requests that page from Colombia (following redirects, and retrying over http if https fails) and keeps only the result for 1 minute.

How to use it

  1. Type the site's address, for example example.com.
  2. Press Check. The address goes to our server in Colombia, which requests the page once and times the answer.
  3. If it's up for us but not for you, the problem is likely your connection, your DNS or a block on your network.

Down for everyone, or only on your network

Your bank's website won't load, a government portal hangs on the last day of a deadline, or a customer says your store is down right after you changed hosting. Before you restart the router or call support, check from somewhere else. Our server in Colombia requests the page once and tells you whether it answered, with what code, and how fast.

If it works for us, the problem is probably on your side: your connection, your DNS, a filter on your network or a block in your country. If it fails for us too, the site itself has a problem, and waiting or telling its owner is all anyone can do.

UP, DOWN and the codes in between

Check tienda-ejemplo.co. A green banner reads UP, tienda-ejemplo.co · HTTP 200 · 850 ms, and the table shows the Final URL https://www.tienda-ejemplo.co/, 2 redirects, HTTPS yes, 850 ms to the first answer and a longer total that includes the redirects. The server is answering normally.

A red DOWN banner comes with the reason: no answer within 5 seconds, a refused connection, a name that doesn't resolve in DNS, too many redirects or an invalid certificate. HTTP 500 or higher also counts as down, because the server is failing for everyone. A 404 or 403 is shown in amber: the server is up, but that page doesn't exist or won't let us in, so check the address. A first answer slower than 3 seconds is marked in amber too. A note that HTTPS failed and we tried plain HTTP means the secure version is broken, even if the page loads.

Why one check doesn't settle it

It's a single request, from one place, at one moment. A site can block other countries or automated visitors and answer us with 403 or an error page while it works for people, and the reverse happens too: a site can work for us and be blocked by your provider. We only check the page you type, on the standard web ports, so the app, the login or the checkout can fail while the homepage loads.

Results are kept for 1 minute, so pressing the button again right away shows the same answer. There's no history and no alerts: to watch your own site around the clock, you need a monitoring service.

FAQ

What counts as down?

No answer within 5 seconds, a refused connection, or a server error (HTTP 500 or higher). A 404 or 403 still means the server is up. If the domain doesn't exist or has no address, we tell you that instead, so check the spelling.

Why is it up here but not for me?

We check from a server in Colombia. Your internet provider, your DNS, a firewall or a regional block can still stop it for you. Try another network or mobile data.

Do you monitor the site over time?

No. We check once, when you press the button, and keep the result for 1 minute so repeated clicks don't flood the site.

What do HTTP 502, 503 and 504 mean?

All three count as down. `502` and `504` usually mean a proxy or CDN in front of the site couldn't get a proper answer from the real server behind it. `503` means the server is overloaded or in maintenance. Either way the fault is on the site's side, not yours.

It works on mobile data but not on my Wi-Fi. Why?

Then the site is fine and the difference is your home network. Common causes are the DNS your router uses, a parental or security filter, or a block by your internet provider. Restart the router, or set a public DNS such as 1.1.1.1 or 8.8.8.8 on your device and try again.

  • 2.1What's my IP?See your public IP address, whether it's IPv4 or IPv6, your country, TLS and HTTP version, and what every website can learn from your connection.
  • 2.2Email securityCheck a domain's SPF, DKIM, DMARC, MTA-STS, BIMI and DNSSEC, and get copy-ready DNS records for what's missing or wrong.
  • 2.3SPF record builderBuild one SPF record for your domain from your mail services, servers and IP ranges.
  • 2.4DNS lookupLook up any domain's DNS records (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV) or the reverse DNS of an IP, with TTLs and DNSSEC validation.
  • 2.5Email header analyzerPaste an email's raw headers to see the servers it passed through, the SPF, DKIM and DMARC results your provider recorded, and signs of a forged sender.
  • 2.6DNS propagation checkerAsk 10 public resolvers (Google, Cloudflare, Quad9, OpenDNS…) for a name's A, AAAA, CNAME, MX, NS or TXT records and see if your DNS change reached them.
  • 2.7DMARC report readerOpen a DMARC aggregate report (.xml, .xml.gz or .zip) and see, for each sending IP, how many messages passed or failed SPF and DKIM.
  • 2.9DMARC record generatorBuild a DMARC TXT record: policy, test mode, report addresses and alignment.
  • 2.10Link preview checkerSee how your link will look when shared on WhatsApp, X, LinkedIn or Facebook: check the title, description, og:image and Twitter card tags, with fixes.
  • 2.11Subnet calculatorType an IP address with its prefix to get the network, mask, broadcast, usable host range and count, and split it into equal subnets.

╌╌ END ╌╌