Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

403 Forbidden

Checks

7 PASS 9 REVIEW

DNS Records

1 A records, 40 ms lookup

REVIEW

1 A records, 40 ms lookup

Resolves to 1 IPv4 address(es)

Got: 150.171.109.101

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2603:1061:14:64::1

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: frontend-noordoostpolder.noordoostpolder.prod.openonline-io.nl

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 40 ms

Got: 40 ms

A	150.171.109.101
AAAA	2603:1061:14:64::1
CNAME	frontend-noordoostpolder.noordoostpolder.prod.openonline-io.nl
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 40 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

Reverse DNS

Action

0/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR lookup failed for 150.171.109.101: lookup 150.171.109.101: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2603:1061:14:64::1: lookup 2603:1061:14:64::1: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: www)

HTTP version does not redirect to HTTPS

Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

200https://www.noordoostpolder.nl/

301https://noordoostpolder.nl/

Preferred variant: www

HTTP → HTTPS

403http://www.noordoostpolder.nl/

HTTP version does not redirect to HTTPS

TLS Certificate Expiry & Recommendations

46 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
Enable DNSSEC on your domain for DNS spoofing protection
Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy

CDN & Delivery

Document on Azure CDN; assets also on CDN77

REVIEW

Document on Azure CDN; assets also on CDN77

Document is served via Azure CDN CDN

Got: x-azure-ref: 20261112T151847Z-176d7f68bd4wjwxphC1FRA9r80000000142g000000002pvu

CDN cache status: CONFIG_NOCACHE

Assets on CDN77: cdn1.readspeaker.com (assets: 5)

Got: delegation 1202598265.rsc.cdn77.org

Document served via CDN: Azure CDN

Provider Azure CDN Cache Status CONFIG_NOCACHE Evidence x-azure-ref: 20261112T151847Z-176d7f68bd4wjwxphC1FRA9r80000000142g000000002pvu

Asset hosts on a CDN

cdn1.readspeaker.com — CDN77 · assets: 5

Other asset hosts

berichten.noordoostpolder.nl — assets: 1 · below probe threshold
siteimproveanalytics.com — assets: 1 · below probe threshold
widget.scribit.pro — assets: 1 · below probe threshold

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

Multi-Resolver DNS Speed

Mean 63ms across 3 resolvers (spread 47ms)

PASS

Mean 63ms across 3 resolvers (spread 47ms)

Google: 45ms

Got: 45ms via 8.8.8.8:53

Cloudflare: 53ms

Got: 53ms via 1.1.1.1:53

Quad9: 92ms

Got: 92ms via 9.9.9.9:53

A+

Redirect Chain

0 redirect(s), 82 ms total

PASS

0 redirect(s), 82 ms total

https://www.noordoostpolder.nl

82 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.noordoostpolder.nl	403	82 ms	HTTP/1.1

A+

IPv6 Readiness

IPv6 reachable (24 ms)

PASS

IPv6 reachable (24 ms)

IPv6 is configured and reachable at 2603:1061:14:64::1

Got: 24 ms connect

IPv6 Ready

AAAA Records 2603:1061:14:64::1 Connection Reachable (24 ms)

A+

HTTP Probe Timing

Total 149 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

72 ms

TCP Connect

24 ms

TLS Handshake

27 ms

Time to First Byte

150 ms

Total Time

150 ms

Connection waterfall

DNS Lookup 72 ms TCP Connect 24 ms TLS Handshake 27 ms Server Processing 26 ms Content Transfer 0 ms

A+

CDN Cache Observability

Cache state: CONFIG_NOCACHE

PASS

Cache state: CONFIG_NOCACHE

CDN cache state observable via 1 header(s)

Got: x-cache=CONFIG_NOCACHE

A+

Health Check Endpoint

Auth-protected health endpoint at https://www.noordoostpolder.nl/health (HTTP 403)

PASS

Auth-protected health endpoint at https://www.noordoostpolder.nl/health (HTTP 403)

Auth-protected health endpoint exposed at https://www.noordoostpolder.nl/health

Got: https://www.noordoostpolder.nl/health

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.