Skip to content
https://Svennouwen.nl

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 85.10.159.51 does not match any cert SAN: 85.10.159.51.nl.transip.me
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2a01:7c8:f0:1051:0:2:b5b8:8a6: lookup 2a01:7c8:f0:1051:0:2:b5b8:8a6: 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.
B
HTTP Probe Timing
Total 867 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
34 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
867 ms
Total Time Total request time from DNS lookup through full response.
868 ms

Connection waterfall

DNS Lookup 45 ms TCP Connect 25 ms TLS Handshake 34 ms Server Processing 763 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
61 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

61
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 85.10.159.51
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a01:7c8:f0:1051:0:2:b5b8:8a6
Info::
3 nameserver(s) configured
Got: ns2.transip.eu, ns1.transip.nl, ns0.transip.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A85.10.159.51
AAAA2a01:7c8:f0:1051:0:2:b5b8:8a6
CNAME—
NSns2.transip.eu, ns1.transip.nl, ns0.transip.net
MX
10 mx.transip.email
TXT
SPF v=spf1 include:_spf.transip.email ~all
CAALookup not available with standard resolver
Resolved in 45 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
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A
Multi-Resolver DNS Speed
Mean 45ms across 3 resolvers (spread 57ms)
PASS
Mean 45ms across 3 resolvers (spread 57ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 38ms
Got: 38ms via 1.1.1.1:53
Info::
Quad9: 77ms
Got: 77ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 443 ms total
PASS
1 redirect(s), 443 ms total
Info::
Single redirect
Got: https://Svennouwen.nl → https://svennouwen.nl/ (301)

https://Svennouwen.nl

157 ms · HTTP/1.1

301

https://svennouwen.nl/

286 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Svennouwen.nl301157 msHTTP/1.1nginx
2https://svennouwen.nl/200286 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2a01:7c8:f0:1051:0:2:b5b8:8a6
Got: 25 ms connect
IPv6 Ready
AAAA Records 2a01:7c8:f0:1051:0:2:b5b8:8a6 Connection Reachable (25 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 114 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

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 200 OK
Size 114 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://svennouwen.nl/wp-sitemap.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.Svennouwen.nl/
200https://Svennouwen.nl/

Preferred variant: non-www

HTTP → HTTPS

301http://Svennouwen.nl/ → https://svennouwen.nl/

Consistent

A+
Domain Intelligence
Svennouwen.nl — via team.blue nl B.V., 4 months old
PASS
Svennouwen.nl — via team.blue nl B.V., 4 months old
Info::
Domain is only 4 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Apr 9, 2026
Info::
Registrar: team.blue nl B.V.
Warning::
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

61 days

Issued by Let's Encrypt

Domain age

4 months

Registered April 9, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a01:7c8:f0:1051:0:2:b5b8:8a6

Registrar

team.blue nl B.V.

Unlocked 3 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar team.blue nl B.V.
Created April 9, 2026 (4 months ago)
Last Updated April 9, 2026
Name Servers ns2.transip.eu, ns1.transip.nl, ns0.transip.net
Hosting
IP Address 2a01:7c8:f0:1051:0:2:b5b8:8a6
Data source: whois (0.8s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

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

Send Feedback