Check 34 of 54 · Domain and registration

Certificates on subdomains, explained.

The certificates on your other hostnames: genuine, issued for the right name and not about to expire.

Engine 1.57.0, read 25 October 2026

Customer scanScoredReliability: High

Could you lose the domain, or part of it?

What the check does, and where it stops.

What it reads

The hosts your mail and SPF records name, then the names a stranger tries first, such as vpn. and remote., then your hostnames from public certificate logs, the most notable first, until 30 still resolve, and the certificate each serves on port 443. One that does not validate, has expired or names another host fails; under 14 days left warns.

Why it matters

An expired or untrusted certificate on a subdomain puts a warning in front of everyone who uses that service.

What a failure looks like

A failure is a finding in your result. The check is scored, so it can lower your score, and the Full Report gives every finding its severity and a fix. If the check cannot finish, it is recorded as unknown: it carries no penalty, and it is never a pass.

Where its limits are

Port 443 only, on at most 30 subdomains. A certificate another provider serves for its own name, or one reached only through your wildcard DNS record, is noted and not charged. A subdomain that does not answer is named as not read.

ReliabilityHigh: narrow, known blind spots

It reads up to 30 of your other hosts, which is more than a check of a domain that is not yet a customer should ask, so it runs on a customer's own verified domains, not on the free check.

Check 34 is one of 10 in Domain and registration. See it in its row on the scanner page, beside the rest of Domain and registration.

See how your domain does.

This check runs on a customer's own verified domains. The free check runs over 40 checks in about 30 seconds, with no account.