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

10 PASS 7 REVIEW

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:63::1: lookup 2603:1061:14:63::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

HTTP version does not redirect to HTTPS

Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.haarlemmermeergemeente.nl/

200https://haarlemmermeergemeente.nl/

HTTP → HTTPS

403http://haarlemmermeergemeente.nl/

HTTP version does not redirect to HTTPS

TLS Certificate Expiry & Recommendations

140 days until leaf cert expires — 1 issues to address

REVIEW

Certificate validity

140

days left

0d 30d 60d 90d+

Recommended actions

Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains

CDN & Delivery

Azure CDN (CONFIG_NOCACHE)

REVIEW

Azure CDN (CONFIG_NOCACHE)

Document is served via Azure CDN CDN

Got: x-azure-ref: 20261112T144822Z-176d7f68bd4966xnhC1FRA1w7g000000124000000000c6qq

CDN cache status: CONFIG_NOCACHE

Document served via CDN: Azure CDN

Provider Azure CDN Cache Status CONFIG_NOCACHE Evidence x-azure-ref: 20261112T144822Z-176d7f68bd4966xnhC1FRA1w7g000000124000000000c6qq

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+

DNS Records

1 A records, 47 ms lookup

PASS

1 A records, 47 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:63::1

3 nameserver(s) configured

Got: ns0.transip.net, ns1.transip.nl, ns2.transip.eu

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 47 ms

Got: 47 ms

A	150.171.109.101
AAAA	2603:1061:14:63::1
CNAME	—
NS	ns0.transip.net, ns1.transip.nl, ns2.transip.eu
MX	10 haarlemmermeergemeente-nl.mail.protection.outlook.com
TXT	MS=ms69507937 SPF v=spf1 include:spf.protection.outlook.com include:spf.emailsys.net ip4:37.97.148... google-site-verification=_1MXqwaxw5t6QxmRVbuTLAgin4s6WlCrWgr7O5Es1kc
CAA	Lookup not available with standard resolver

Resolved in 47 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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

DNSSEC

Signed and validating

PASS

Signed and validating

DNSSEC fully signed and chain validates (ECDSAP256SHA256)

Multi-Resolver DNS Speed

Mean 55ms across 3 resolvers (spread 47ms)

PASS

Mean 55ms across 3 resolvers (spread 47ms)

Cloudflare: 39ms

Got: 39ms via 1.1.1.1:53

Google: 40ms

Got: 40ms via 8.8.8.8:53

Quad9: 86ms

Got: 86ms via 9.9.9.9:53

A+

Redirect Chain

0 redirect(s), 86 ms total

PASS

0 redirect(s), 86 ms total

https://haarlemmermeergemeente.nl

86 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://haarlemmermeergemeente.nl	403	86 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:63::1

Got: 24 ms connect

IPv6 Ready

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

A+

Domain Intelligence

haarlemmermeergemeente.nl — via team.blue nl B.V., 11 years, 8 months old

PASS

haarlemmermeergemeente.nl — via team.blue nl B.V., 11 years, 8 months old

DNSSEC is enabled

Registrar: team.blue nl B.V.

Registrar lock is NOT enabled

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Domain expiry

Unknown

SSL certificate

140 days

Issued by Sectigo Limited

Domain age

11 years, 8 months

Registered April 23, 2015

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2603:1061:14:63::1

Registrar

team.blue nl B.V.

Unlocked 3 NS records

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar team.blue nl B.V.

Created April 23, 2015 (11 years, 8 months ago)

Last Updated February 6, 2024

Name Servers ns0.transip.net, ns1.transip.nl, ns2.transip.eu

DNSSEC Enabled

Registrant REDACTED FOR PRIVACY

Hosting

IP Address 2603:1061:14:63::1

Data source: rdap (0.6s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+

HTTP Probe Timing

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

PASS

DNS Lookup

41 ms

TCP Connect

25 ms

TLS Handshake

32 ms

Time to First Byte

124 ms

Total Time

124 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 25 ms TLS Handshake 32 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://haarlemmermeergemeente.nl/health (HTTP 403)

PASS

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

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

Got: https://haarlemmermeergemeente.nl/health

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