| Check | What changed | Observed |
|---|---|---|
| SPF permitted senders | New SPF senders
What to do Identify which tool or provider added itself to the SPF record, using the include named above. If the client uses that tool, mark the change as expected; if not, remove the include from the SPF record.
|
first seen 2026-08-10 06:00 UTC confirmed 2026-08-10 12:00 UTC |
| Security headers | Content-Security-Policy: directive frame-ancestors removed
What to do Restore the header in the web server, CDN or application configuration. It was most likely dropped during a deployment.
|
first seen 2026-08-10 06:00 UTC confirmed 2026-08-10 12:00 UTC |
| Certificate transparency | Certificate issued by an authority not seen before
What to do Find out who asked for it. If the client or their host moved to a new certificate authority, or turned on a CDN or a new hosting platform, this is expected: mark it so. If nobody recognises it, treat it as urgent: someone may have proved control of the domain or a subdomain. Check the DNS zone and the registrar account for changes, and who has access to both.
|
first seen 2026-08-22 00:00 UTC confirmed 2026-08-23 00:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| Mail servers (MX) | MX records changed
|
first seen 2026-08-10 06:00 UTC confirmed 2026-08-10 12:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| Certificate transparency | Certificate authorities recorded
What to do No action needed. This is a record of which authorities have issued for the domain.
|
first seen 2026-08-01 00:00 UTC |
| Website address (A) | A records changed
What to do Address changes are normal for hosts behind a CDN. If the site is not on a CDN, confirm the new address with the hosting provider.
|
first seen 2026-08-03 00:00 UTC |
| Check | Observed value |
|---|---|
| Website address (A) | 192.0.2.12, 192.0.2.13 |
| Blocklist status | (none) |
| Alias targets (CNAME) | (none) |
| DNSSEC | (none) |
| Mail servers (MX) | 10 aspmx.bigmail.test, 20 alt1.aspmx.bigmail.test |
| Nameservers | ns1.dnshost.test, ns2.dnshost.test |
| Domain registration | expires 2027-04-18T00:00:00Z; registrar Example Registrar Ltd; locked |
| DKIM selector mh1 | present, rsa 2048 bits |
| DMARC policy | p=quarantine, pct=100, published at the exact name |
| SPF permitted senders | 5 permitted senders; ends -all; 4 lookups |
| Home page | status 200; 48213 bytes; indexable; no mixed content; found expected text 'Order your cake' |
| Security headers | 8 security headers present |
| HTTP to HTTPS redirect | redirects; status 301 |
| security.txt | published; contact mailto:security@acme-bakery.test |
| HTTPS certificate | valid until 2026-11-28T00:00:00Z (Example CA R3) |
| Certificate transparency | 4 unexpired certificate(s) from 2 authority(ies): Example CA, Budget Certs Inc |
| TLS versions accepted | lowest accepted TLSv1.2 |
| Check | Status | Last successful observation |
|---|---|---|
| Website address (A) | observed | 2026-08-31 18:00 UTC |
| Blocklist status | observed | 2026-08-31 18:00 UTC |
| Alias targets (CNAME) | observed | 2026-08-31 18:00 UTC |
| DNSSEC | observed | 2026-08-31 18:00 UTC |
| Mail servers (MX) | observed | 2026-08-31 18:00 UTC |
| Nameservers | observed | 2026-08-31 18:00 UTC |
| Domain registration | observed | 2026-08-31 18:00 UTC |
| DKIM selector mh1 | observed | 2026-08-31 18:00 UTC |
| DMARC policy | observed | 2026-08-31 18:00 UTC |
| SPF permitted senders | observed | 2026-08-31 18:00 UTC |
| Home page | observed | 2026-08-31 18:00 UTC |
| Security headers | observed | 2026-08-31 18:00 UTC |
| HTTP to HTTPS redirect | observed | 2026-08-31 18:00 UTC |
| security.txt | observed | 2026-08-31 18:00 UTC |
| HTTPS certificate | observed | 2026-08-31 18:00 UTC |
| Certificate transparency | stale | 2026-08-23 00:00 UTC |
| TLS versions accepted | observed | 2026-08-31 18:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| DKIM selector selector1 | DKIM selector selector1 removed
What to do Check the mail provider's DKIM settings. If the client changed mail providers, add the new selector here and remove the old one; if not, the DNS record may have been deleted by mistake.
|
first seen 2026-08-18 12:00 UTC confirmed 2026-08-18 18:00 UTC |
| Home page | Search engines are told not to index the home page
What to do Almost always a staging setting that reached production. In WordPress, Settings then Reading, clear "Discourage search engines". Otherwise remove the noindex from the meta robots tag or the X-Robots-Tag header at the server or CDN. Until it is removed the site will drop out of search results.
|
first seen 2026-08-18 12:00 UTC confirmed 2026-08-18 18:00 UTC |
| Home page | Page loads resources over plain http
What to do Change the listed sources to https, or serve them from the site itself. Browsers block insecure scripts and stylesheets on a secure page, so part of the design or behaviour is probably already broken, and the padlock is weakened.
|
first seen 2026-08-18 12:00 UTC confirmed 2026-08-18 18:00 UTC |
| Blocklist status | Address listed on a blocklist
What to do Find out why the address was listed (the blocklist's lookup page names the reason), fix the cause, then request delisting there. For a shared hosting or mail address, ask the provider; they usually handle delisting. Mail from a listed mail server is likely to be rejected or filtered until it is cleared.
|
first seen 2026-08-25 00:00 UTC confirmed 2026-08-25 06:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| HTTPS certificate | Certificate expires within 14 days
What to do Renew the certificate before the date shown. If renewal is automatic, check that the renewal job is running and that DNS or HTTP validation still succeeds.
|
first seen 2026-08-31 18:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| Domain registration | Domain registration expires within 60 days
What to do Renew the domain at the registrar before the date shown, or confirm auto-renew is on and the payment method is valid. An expired domain takes the website and email with it.
|
first seen 2026-08-31 18:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| DMARC policy | DMARC policy inherited from organisational domain
What to do No action needed. The subdomain uses the parent domain's policy; publish a record at the subdomain only if it should differ.
|
first seen 2026-08-01 00:00 UTC |
| Security headers | Content-Security-Policy not set
What to do Optional: add this header at the web server or CDN. Hosting providers and CDNs usually have a one-line setting for it.
|
first seen 2026-08-01 00:00 UTC |
| Security headers | X-Frame-Options not set
What to do Optional: add this header at the web server or CDN. Hosting providers and CDNs usually have a one-line setting for it.
|
first seen 2026-08-01 00:00 UTC |
| Security headers | Permissions-Policy not set
What to do Optional: add this header at the web server or CDN. Hosting providers and CDNs usually have a one-line setting for it.
|
first seen 2026-08-01 00:00 UTC |
| Security headers | Cross-Origin-Resource-Policy not set
What to do Optional: add this header at the web server or CDN. Hosting providers and CDNs usually have a one-line setting for it.
|
first seen 2026-08-01 00:00 UTC |
| Domain registration | Registrar transfer lock not set
What to do Enable the registrar transfer lock so the domain cannot be moved without unlocking it first.
|
first seen 2026-08-01 00:00 UTC |
| DNSSEC | DNSSEC not enabled
What to do Optional: enabling DNSSEC at the DNS host and publishing the DS record at the registrar protects answers from tampering. Only do this if the DNS host supports it fully.
|
first seen 2026-08-01 00:00 UTC |
| Check | Observed difference | First seen |
|---|---|---|
| Home page | Search engines are told not to index the home page | 2026-08-31 18:00 UTC |
| Home page | Page loads resources over plain http | 2026-08-31 18:00 UTC |
| Blocklist status | Address listed on a blocklist | 2026-08-31 18:00 UTC |
| Check | Observed value |
|---|---|
| Blocklist status | (none) |
| Website alias (CNAME) | shops.platform-host.test |
| DNSSEC | no record |
| Mail servers (MX) | 10 mx.harbour-goods.test |
| Domain registration | expires 2026-10-02T00:00:00Z; registrar Example Registrar Ltd; no transfer lock |
| DKIM selector google | no record |
| DKIM selector selector1 | no record |
| DMARC policy | p=quarantine, pct=100, inherited from harbour-goods.test |
| SPF permitted senders | 1 permitted sender; ends ~all; 1 lookups |
| Home page | status 200; 30102 bytes; NOT INDEXABLE; 1 insecure source(s) |
| Security headers | 4 security headers present |
| HTTP to HTTPS redirect | redirects; status 308 |
| HTTPS certificate | valid until 2026-09-12T00:00:00Z (Example CA R3) |
| TLS versions accepted | lowest accepted TLSv1.2 |
| Check | Status | Last successful observation |
|---|---|---|
| Blocklist status | observed | 2026-08-31 18:00 UTC |
| Website alias (CNAME) | observed | 2026-08-31 18:00 UTC |
| DNSSEC | observed | 2026-08-31 18:00 UTC |
| Mail servers (MX) | observed | 2026-08-31 18:00 UTC |
| Domain registration | observed | 2026-08-31 18:00 UTC |
| DKIM selector google | observed | 2026-08-31 18:00 UTC |
| DKIM selector selector1 | observed | 2026-08-31 18:00 UTC |
| DMARC policy | observed | 2026-08-31 18:00 UTC |
| SPF permitted senders | observed | 2026-08-31 18:00 UTC |
| Home page | observed | 2026-08-31 18:00 UTC |
| Security headers | observed | 2026-08-31 18:00 UTC |
| HTTP to HTTPS redirect | observed | 2026-08-31 18:00 UTC |
| HTTPS certificate | observed | 2026-08-31 18:00 UTC |
| TLS versions accepted | observed | 2026-08-31 18:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| HTTPS certificate | Certificate expires within 30 days
What to do Renew the certificate before the date shown. If renewal is automatic, check that the renewal job is running and that DNS or HTTP validation still succeeds.
|
first seen 2026-08-31 18:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| Domain registration | Domain registration expires within 30 days
What to do Renew the domain at the registrar before the date shown, or confirm auto-renew is on and the payment method is valid. An expired domain takes the website and email with it.
|
first seen 2026-08-31 18:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| DMARC policy | No DMARC record observed
What to do Publish a DMARC record at _dmarc.<domain>, starting with p=none and a reporting address, once SPF and DKIM are in place.
|
first seen 2026-08-01 00:00 UTC |
| Domain registration | Registrar transfer lock not set
What to do Enable the registrar transfer lock so the domain cannot be moved without unlocking it first.
|
first seen 2026-08-01 00:00 UTC |
| DNSSEC | DNSSEC not enabled
What to do Optional: enabling DNSSEC at the DNS host and publishing the DS record at the registrar protects answers from tampering. Only do this if the DNS host supports it fully.
|
first seen 2026-08-01 00:00 UTC |
| TLS versions accepted | Legacy TLS versions accepted
What to do Ask the hosting provider to disable TLS 1.0 and 1.1. Modern browsers no longer use them and they weaken the connection for everyone.
|
first seen 2026-08-01 00:00 UTC |
| security.txt | No security.txt published
What to do Optional: publish /.well-known/security.txt with a contact address so anyone who finds a problem knows whom to tell.
|
first seen 2026-08-01 00:00 UTC |
| Check | What changed | Observed |
|---|---|---|
| Security headers | Check has not succeeded for 12 hours
What to do No action on the client's domain: the check itself could not complete. If it persists for more than a day, contact support with the domain name.
|
first seen 2026-08-19 18:00 UTC confirmed 2026-08-20 06:00 UTC |
| Check | Observed value |
|---|---|
| Website address (A) | 198.51.100.20 |
| DNSSEC | no record |
| Mail servers (MX) | 10 mail.bluefin-legal.test |
| Domain registration | expires 2026-09-18T00:00:00Z; registrar Example Registrar Ltd; no transfer lock |
| DMARC policy | no record |
| SPF permitted senders | 1 permitted sender; ends -all; 1 lookups |
| Availability | up · status 200 · 196 ms |
| Security headers | 8 security headers present |
| HTTP to HTTPS redirect | redirects; status 301 |
| security.txt | no record |
| HTTPS certificate | valid until 2026-09-29T00:00:00Z (Example CA R3) |
| TLS versions accepted | lowest accepted TLSv1; legacy versions accepted |
| Check | Status | Last successful observation |
|---|---|---|
| Website address (A) | observed | 2026-08-31 18:00 UTC |
| DNSSEC | observed | 2026-08-31 18:00 UTC |
| Mail servers (MX) | observed | 2026-08-31 18:00 UTC |
| Domain registration | observed | 2026-08-31 18:00 UTC |
| DMARC policy | observed | 2026-08-31 18:00 UTC |
| SPF permitted senders | observed | 2026-08-31 18:00 UTC |
| Availability | observed | 2026-08-31 18:00 UTC |
| Security headers | stale | 2026-08-19 18:00 UTC |
| HTTP to HTTPS redirect | observed | 2026-08-31 18:00 UTC |
| security.txt | observed | 2026-08-31 18:00 UTC |
| HTTPS certificate | observed | 2026-08-31 18:00 UTC |
| TLS versions accepted | observed | 2026-08-31 18:00 UTC |