Who is hosting this site — hosting and DNS checker

See what a website actually runs on: nameservers, A and AAAA records, CDN fingerprints, DNSSEC, the CAA record, HTTP/3 support and real availability. We read public DNS and one server response, so it works for any domain — including one you do not own.

What the hosting check covers

Availability and DNS correctness — Whether the home page responds at all, and whether the domain resolves correctly. These carry the heaviest weight in the pillar, because no other measurement matters while the server is down. We also report inconsistent and failing DNS answers.

Redundancy — how many single points of failure — We count A records and nameservers. One IP and one NS mean a single machine failure takes the whole site down along with its DNS. Two independent nameservers are standard with most registrars and usually a single setting away.

CDN, HTTP/3 and IPv6 — Content delivery network fingerprints, HTTP/3 support detected through the alt-svc header, and whether AAAA records exist. All three are conveniences rather than requirements — we score them gently and say plainly that their absence is not a fault.

DNSSEC and CAA — A DNSSEC signature protects against forged DNS answers, and a CAA record restricts which certificate authority may issue a certificate for your domain. Both are available from most providers and both are rarely switched on.

Identifying a hosting provider from the outside is inference, not fact. An IP block belongs to whoever announces it — and behind a CDN that is the CDN, not the origin server. So we report what we observed (nameservers, IP addresses, the announcing organisation, CDN fingerprints) rather than presenting a guessed company name as certain. We also do not measure uptime: one scan shows one moment, not a month of history. Weightings are in the methodology.

What these results say about your hosting

A single NS record. The most serious weakness we see, and the cheapest to fix. When one machine serves your DNS and that machine goes down, the domain ceases to exist for the world — website, email and everything else under it. Most providers have a second nameserver ready to enable.

No DNSSEC. Without a signature, DNS answers can be forged in transit and send visitors somewhere else while the browser bar still shows the right name. Enabling it needs support from both your DNS provider and your registrar, but it is usually one switch on each side.

No CAA record. Without it, any public certificate authority may issue a certificate for your domain. CAA narrows that list to the ones you name, and it is a single TXT record.

No CDN. This is not a fault, and plenty of excellent sites run without one. It matters when your audience is geographically spread or your traffic is uneven — then a CDN shortens response times and absorbs the peaks.

When the problem really is the hosting

A slow site does not always mean a weak server, and the split is easy to make. High TTFB with a light page points at the server or database. Low TTFB with a page that still takes forever points at the assets — images, scripts, fonts — and changing host will fix nothing.

The second clear signal is variance. A shared server under load returns very different response times from one measurement to the next, while a dedicated resource holds steady. A scan captures one measurement, so if you suspect variance, repeat it at different times of day.

The third is 5xx errors under ordinary traffic. That is no longer an optimisation question but a mismatch between resources and load.

Before you change host

1. Check that migrating solves your actual problem Compare TTFB against page weight. A light page with high TTFB will benefit from migration. A heavy page with low TTFB will not, because the bottleneck is the front end.

2. Lower your record TTLs before the move A day ahead, set a short TTL so the change propagates quickly and a rollback would too. Restore the defaults once the migration has settled.

yourdomain.com  300  IN  A  203.0.113.10

3. Move email deliberately MX, SPF, DKIM and DMARC records do not travel with the website. A migrated site with forgotten mail records is the most common reason for a silent inbox the next morning. Check yours with the email authentication test.

4. Verify the result afterwards Once the switch is live, run the scan again and compare availability, TTFB, nameserver count and the certificate. A new host is sometimes faster and worse configured at the same time.

Frequently asked questions

Can you always tell who hosts a given website? No, and it is worth saying so plainly. We can see the IP address, the organisation announcing that block, and the nameservers. When a site sits behind a CDN, the address belongs to the CDN and the origin server stays hidden. That is why we show observed facts rather than presenting a guessed provider name as certain.

Does hosting affect Google rankings? Indirectly. Google does not grade your provider, but it does measure the consequences: server response time feeds into Core Web Vitals, and being unreachable when the crawler visits makes indexing harder. Server location matters far less today than language signals and CDNs.

Do I need IPv6, HTTP/3 and a CDN? None of the three is required, and a great many well-functioning sites have none of them. They are conveniences: IPv6 is invisible to the visitor, HTTP/3 shortens connection setup on poor networks, and a CDN helps with a geographically spread audience or uneven traffic. That is exactly why we score them gently.

Why does the result mention two nameservers when I have one provider? It counts nameservers, not companies. Most providers give you at least two (ns1 and ns2) within a single service, and that is entirely sufficient. The warning only appears when we see one NS in the response, which makes DNS a single point of failure.

Is the check free, and do I need an account? It is free and requires no login or email address. Hosting and DNS is one of the eight pillars in a full SEOMaster audit.

Email authentication test · Page speed test · Security headers test