aadsboard.56 free tools

A domain, DNS and HTTPS checkup for business owners

Separate registration, website routing, mail records and certificate checks so you can ask a provider the right question without changing unrelated settings.

By Adsboard · Updated November 19, 2026 · 3 minute read

“My domain is broken” can describe several unrelated problems. Registration determines the right to use the name, DNS tells services where to connect, hosting serves the page and HTTPS certificates protect the connection. Email adds another set of records. Check these layers separately before changing configuration.

Registration: who manages the domain?

Use the RDAP lookup for public registrar, event, status and nameserver information. Keep the date and domain with the report. Registration, update and expiry events are different fields. Privacy redaction does not mean nobody owns the domain, and an expiry event alone does not establish that it is available for purchase.

If you are investigating renewal, use the registrar’s authenticated account and support channels. Do not rely on an unsolicited renewal message merely because it contains public domain information.

Delegation: where should DNS changes happen?

The nameserver lookup can help identify the published DNS provider. A registrar, DNS provider and web host can be three different companies. Changing records in a panel that is not authoritative may have no public effect.

Before moving nameservers, record the complete required zone. Website, email and verification services may all depend on records that are easy to overlook. Avoid replacing working settings just to make several provider names match.

Website routing: check both address families

Use the A and AAAA lookup for the exact hostname visitors use. The root domain and www can have different values. Compare the returned addresses with the intended configuration, allowing for a deliberate proxy or CDN. An address that differs from the origin server is not automatically wrong.

Check IPv6 as well as IPv4. An old AAAA record can send some clients to a different destination. Public resolver answers can be cached, so a recently changed record may not look identical everywhere immediately. Verify the actual site connection after the DNS review.

Email routing is a separate task

MX records advertise mail routing. A working website does not prove mail is configured. TXT records can support site verification, SPF and other services; the TXT lookup shows published values, not whether a receiving service has accepted them.

The SPF and DMARC checkers reveal policies. They do not validate every legitimate sender, simulate all mail delivery or guarantee inbox placement. Inventory sending services and review real-message authentication results with your mail provider before tightening policy.

HTTPS: inspect the hostname being served

The SSL / TLS test reports the certificate seen on one connection. Check hostname coverage, trust verification and expiry. A root-domain certificate does not necessarily cover every subdomain. A successful certificate check also does not certify the business or rule out other security problems.

Make a provider request with evidence

Record the exact hostname, date, expected value and observed problem. “The www hostname returns this certificate, but visitors use a different hostname” is more actionable than “SSL is broken”. Keep sensitive account information out of public tool inputs. Change one layer intentionally and retest the service it affects, preserving the previous working settings for recovery.

Continue with a practical task

Browse all guides or choose a free tool. All examples are illustrative; replace assumptions with your own verified details.