Network Tools
When a site will not load, email bounces after a DNS change, or a domain is about to lapse, you need an answer from outside your own network. These six tools look up DNS records, domain registration data and IP locations, and check a URL's status code, response time, SSL certificate and redirect chain, without installing dig, curl or a whois client.
Named data sources
DNS answers come from Google Public DNS, domain records from the registry's official RDAP service, and IP locations from ipinfo.io. You can judge each result by its source.
Who handles your query
DNS and IP lookups go from your browser to Google Public DNS or ipinfo.io. Whois, status and redirect checks go through our server. None of them needs an account.
An outside view of your site
The status and redirect checkers request your URL from our server, so they show what the public internet sees, not what your own network, VPN or browser cache shows.
Guard rails on the server
Server-side checks refuse private, local and reserved addresses, follow at most 10 redirects, wait up to 8 seconds per hop, send no cookies or credentials, and are rate limited.
The tools most visitors start with, and what each one is for.
Check website status and HTTP response codes.
Confirm whether a website is reachable right now, with its status code, response time, server header and SSL certificate state.
Look up DNS records for any domain.
Query the A, AAAA, CNAME, MX, NS, TXT, SOA, SRV or CAA records of a domain and read each record's TTL.
Check URL redirects and redirect chains.
Trace every hop from a URL to its final destination and get warnings about long chains, loops and temporary redirects.
Find your public IP address and location details.
Find the public IP address your connection shows to websites, with its approximate location and network provider, for example to confirm a VPN is on.
Check domain registration details.
Check a domain's registrar, registration and expiry dates, name servers, DNSSEC status and registry status codes.
Find geographic location of IP addresses.
Look up the city, region, country, time zone and network operator behind any IP address from a log or an email header.
Short explainers that show how the maths or the file format works, and which tool to reach for next.
Network Guides
A step-by-step way to find out why a site is down or misbehaving: check DNS records, then the HTTP status code and redirect chain, then domain expiry and your own IP.
Try it: DNS Lookup
Each group explains what its tools are for, so you can find the right one without scrolling a long list.
Find the public IP address your connection uses and its approximate location, or look up the city, region, country, time zone and network operator for any other IP address.
Read the DNS records that decide where a domain's website and email go, and the registration record that shows its registrar, expiry date and name servers.
Request a URL from our server to see whether it answers, how quickly, with which status code and certificate, and where redirects send a visitor before the final page loads.
Step from does it resolve, to does it answer, to where does it redirect, to when does the domain expire, in a few minutes and without a terminal, dig, curl or a whois client.
Status codes come with a name and a meaning, redirect chains with advice on permanent versus temporary redirects, registry status codes with explanations, and SSL certificates with the days remaining.
Because the status and redirect requests come from our server, they bypass your browser cache, VPN, corporate proxy and local DNS, which often explain a site that only fails for you.
Before and after moving a domain or host, compare DNS records, confirm that each old URL redirects once to the right place, and check the expiry date so the registration cannot lapse unnoticed.
Each page notes what it cannot do: checks run from one location, only public http and https addresses on standard ports work, JavaScript redirects are not followed, and IP locations are approximate.
Each network tool is tied to one named source, so you can judge the answer. DNS Lookup queries Google Public DNS over HTTPS for nine record types. Whois Lookup finds the right registry through the IANA RDAP bootstrap file, which the server caches for 24 hours, then asks that registry directly. The Server Status Checker, Redirect Checker and HTTP Status Checker share one server-side route and one table of status code explanations, so they never disagree. That route checks the resolved addresses before connecting, re-checks every redirect target, and reads response headers only. The IP tools use ipinfo.io, whose locations are approximate by nature.
IP geolocation is inferred from registration and routing data, not from your device, so it often points to your internet provider's regional hub rather than your street. A VPN or mobile network can show another city or even another country. The tools show the city, region, country, coordinates, time zone and postal code that ipinfo.io returns, so treat them as approximate.
DNS answers are cached for the record's TTL, shown in seconds next to each result. The tool asks Google Public DNS, which may keep serving the previous value until that time passes, and your own provider's resolver can differ again. Before a planned change, lower the TTL in advance, then look the record up again once the old TTL has expired.
It reads the registry's RDAP service, and most registries now hide owner names, emails and phone numbers for privacy. You still get the registrar, registration and expiry dates, the last change, name servers, DNSSEC status and status codes explained. A few country-code extensions do not publish RDAP data at all and cannot be looked up here.
Only if it is reachable from the public internet. The request is made from our server, which refuses localhost, .local and .internal names, private and reserved IP addresses, URLs containing a username or password, and ports other than 80, 443, 8080 and 8443. A staging site behind a login or VPN has to be checked from inside that network.
One redirect is normal, such as HTTP to HTTPS. Two are worth fixing, and three or more slow the page and can dilute SEO value, so the Redirect Checker flags them. It also separates permanent redirects (301, 308) from temporary ones (302, 303, 307) and follows up to 10 hops before reporting a possible loop.
No. The server answered, so it is up, but it refused or rate limited the automated request. Try switching the method between GET and HEAD, or set Identify as to Chrome browser. A persistent 403 or 429 usually means the site or its CDN blocks automated checks, which does not necessarily affect real visitors.
Includes JSON Formatter, JSON Validator, JWT Decoder and more.
33 tools →
Includes Meta Title Generator, Meta Description Generator, Schema Markup Generator and more.
20 tools →
Includes HTML Validator, JSON Schema Validator, CSS Validator and more.
15 tools →
Looking for something that is not here? Tell us which tool you need, or browse all tools.