Skip to content
https://biermetstijl.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
17
8 PASS 8 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a01:448:4005::31
Info::
IPv6 connection error
Got: dial tcp6 [2a01:448:4005::31]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a01:448:4005::31 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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).
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 194.213.127.31 does not match any cert SAN: server071.mijndomeinhosting.nl
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 for 2a01:448:4005::31 does not match any cert SAN: server071.mijndomeinhosting.nl
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.
B
Redirect Chain
2 redirect(s), 737 ms total
REVIEW
2 redirect(s), 737 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://biermetstijl.com
Info::
Redirect overhead: 737 ms total
Got: 737 ms
Info::
Cross-domain redirect detected

https://biermetstijl.com

444 ms · HTTP/1.1

302

https://mijndomein.zendesk.com/hc/nl/art...

263 ms · HTTP/1.1

301

https://mijndomein.zendesk.com/hc/nl/art...

31 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://biermetstijl.com302444 msHTTP/1.1nginx
2https://mijndomein.zendesk.com/hc/nl/art...301263 msHTTP/1.1cloudflare
3https://mijndomein.zendesk.com/hc/nl/art...20031 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 10240 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 10240 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!DOCTYPE html>
<html dir="ltr" lang="nl">
<head>
  <meta charset="utf-8" />
  <!-- v28080 -->


  <title>Beveiligingsupdate MijnAccount, Mijndomein, Webhosting &amp; Webmail; PHP-kwetsbaarheden ( CVE-2026-109618 / CVE-2026-109619 ) &ndash; Mijndomein Helpdesk</title>

  

  <meta name="description" content="Jouw veiligheid gaat voor  Jouw veiligheid gaat voor. Daarom zijn onze websites en die van onze klanten tijdelijk offline.Er is een..." /><meta property="og:image" content="https://mijndomein.zendesk.com/hc/theming_assets/01M4G56ZQXBR6HC228KWCG2940" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Mijndomein Helpdesk" />
<meta property="og:title" content="Beveiligingsupdate MijnAccount, Mijndomein, Webhosting &amp; Webmail; PHP-kwetsbaarheden ( CVE-2026-109618 / CVE-2026-109619 )" />
<meta property="og:description" content="Jouw veiligheid gaat voor

Jouw veiligheid gaat voor.
Daarom zijn onze websites en die van onze klanten tijdelijk offline.Er is een ernstig beveiligingslek ontdekt in PHP, een technologie die werel..." />
<meta property="og:url" content="https://mijndomein.zendesk.com/hc/nl/articles/40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-Webmail-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619" />
<link rel="canonical" href="https://mijndomein.zendesk.com/hc/nl/articles/40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-Webmail-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619">
<link rel="alternate" hreflang="nl" href="https://mijndomein.zendesk.com/hc/nl/articles/40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-Webmail-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619">
<link rel="alternate" hreflang="x-default" href="https://mijndomein.zendesk.com/hc/nl/articles/40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-Webmail-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619">

  <link rel="stylesheet" href="//static.zdassets.com/hc/assets/application-b925b7498ff4356827db8a6064e91e2b.css" media="all" id="stylesheet" />
  <link rel="stylesheet" type="text/css" href="/hc/theming_assets/301156/29521/style.css?digest=40011676757010">

  <link rel="icon" type="image/x-icon" href="/hc/theming_assets/01M4G5702WGEH6EGEKMNBV114A">

    

  <meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="theme-color" content="#24103A">

  <link rel="icon" href="/hc/theming_assets/01M4G5702WGEH6EGEKMNBV114A">

<!--
  Circular Std is the approved Mijndomein typeface. The scaffold references the family in CSS,
  but licensed font binaries are intentionally not bundled here. Add the licensed webfont files
  as Guide theme assets and declare @font-face in style.css before production launch.
-->

<!-- Safe, narrow integration configuration. No arbitrary HTML/JS is accepted from theme settings. -->

  <meta name="md-google-tag-id" content="GTM-T3P74VX">
  <script>
    (function () {
      var node = document.querySelector('meta[name="md-google-tag-id"]');
      var id = node ? String(node.getAttribute('content') || '').trim() : '';
      if (!/^(GTM-[A-Z0-9-]+|G-[A-Z0-9]+)$/i.test(id)) {
        if (id) console.warn('[Mijndomein Helpdesk] Ignoring invalid Google tag ID.');
        return;
      }

      if (/^GTM-/i.test(id)) {
        window.dataLayer = window.dataLayer || [];
        window.dataLayer.push({'gtm.start': new Date().getTime(), event:'gtm.js'});
        var script = document.createElement('script');
        script.async = true;
        script.src = 'https://www.googletagmanager.com/gtm.js?id=' + encodeURIComponent(id);
        (document.head || document.documentElement).appendChild(script);
        return;
      }

      window.dataLayer = window.dataLayer || [];
      window.gtag = window.gtag || function () { window.dataLayer.push(arguments); };
      window.gtag('js', new Date());
      window.gtag('config', id);
      var script = document.createElement('script');
      script.async = true;
      script.src = 'https://www.googletagmanager.com/gtag/js?id=' + encodeURIComponent(id);
      (document.head || document.documentElement).appendChild(script);
    }());
  </script>


<!-- Messaging availability configuration. The theme never stores Zendesk API credentials client-side. -->
<meta name="md-messaging-enabled" content="false">
<meta name="md-messaging-use-business-hours" content="false">
<meta name="md-messaging-business-days" content="1,2,3,4,5">
<meta name="md-messaging-business-windows" content="09:00-12:00,13:00-16:00">
<meta name="md-messaging-business-timezone" content="Europe/Amsterdam">
<meta name="md-messaging-availability-endpoint" content="">
<meta name="md-messaging-offline-text" content="Domeintje helpt je direct. Is een medewerker nodig? Dan reageren we zo snel mogelijk en kun je het gesprek voortzetten wanneer het jou uitkomt.">

  
</head>
<body class="">
  
  
  

  <a class="skip-navigation" href="#main-content">Overslaan en naar hoofdcontent gaan</a>

  <div class="top-alert top-alert--critical" role="status">
    <div class="container">
      <span class="alert-dot" aria-hidden="true"></span>
      <span>
        <strong>We nemen preventieve beveiligingsmaatregelen</strong>
         Hierdoor is onze mijndomein.nl en MijnAccount, webhosting en webmail tijdelijk niet beschikbaar. E-mailverkeer, Websitemaker en Webshop blijven werken.
        
          <a class="alert-link" href="https://mijndomein.zendesk.com/hc/nl/articles/40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619" data-configured-url>Bekijk de status hier.</a>
        
      </span>
    </div>
  </div>


<header class="site-header">
  <div class="container header-inner">
    <a class="brand brand-logo-link" title="Start" href="/hc/nl">
      
        <img class="zd-logo" src="/hc/theming_assets/01M4G56ZQXBR6HC228KWCG2940" alt="Mijndomein">
      
    </a>

    <nav class="nav" aria-label="Hoofdnavigatie">
      <a href="https://nieuws.mijndomein.nl/">Blog</a>
      <a href="/hc/nl/p/onboarding">Aan de slag</a>
      
        <a href="/hc/nl/p/community">Community</a>
      
      <a href="/hc/nl/p/contact">Contact</a>
    </nav>

    <div class="header-actions">
      
        <a class="btn btn-primary" role="link" rel="nofollow" data-auth-action="signin" title="Wordt in een dialoogvenster geopend" href="/hc/nl/signin?return_to=https%3A%2F%2Fmijndomein.zendesk.com%2Fhc%2Fnl%2Farticles%2F40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-Webmail-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619">Inloggen</a>
      
      <button class="mobile-menu" type="button" aria-label="Menu" aria-expanded="false" data-mobile-menu>☰</button>
    </div>
  </div>

  <nav class="mobile-nav" data-mobile-nav aria-label="Mobiele navigatie">
    
      <a class="mobile-sign-in" role="link" rel="nofollow" data-auth-action="signin" title="Wordt in een dialoogvenster geopend" href="/hc/nl/signin?return_to=https%3A%2F%2Fmijndomein.zendesk.com%2Fhc%2Fnl%2Farticles%2F40010485409170-Beveiligingsupdate-MijnAccount-Mijndomein-Webhosting-Webmail-PHP-kwetsbaarheden-CVE-2026-109618-CVE-2026-109619">Inloggen</a>
      <span class="mobile-nav-divider"></span>
    
    <a href="/hc/nl/p/contact">Contact</a>
    <a href="https://nieuws.mijndomein.nl/">Blog</a>
    <a href="/hc/nl/p/onboarding">Aan de slag</a>
    
      <a href="/hc/nl/p/community">Community</a>
    
  </nav>
</header>


  <main role="main">
    <main id="main-content">
  <div class="container page-breadcrumbs"><nav aria-label="Broodkruimel">
  <ol class="breadcrumbs">
    
      <li>
        
          <a href="/hc/nl">Mijndomein Helpdesk</a>
        
      </li>
    
      <li>
        
          <a href="/hc/nl/categories/360003429258-Actuele-Status">Actuele Status</a>
        
      </li>
    
      <li>
        
          <a href="/hc/nl/sections/360005235238-Verstoringen">Verstoringen</a>
        
      </li>
    
  </ol>
</nav>
</div>
  <div class="container article-layout">
    <article class="article">
      <h1>Beveiligingsupdate MijnAccount, Mijndomein, Webhosting &amp; Webmail; PHP-kwetsbaarheden ( CVE-2026-109618 / CVE-2026-109619 )</h1>
      <div class="article-meta-row" aria-label="Artikelinformatie">
        <span>Bijgewerkt <time datetime="2026-10-21T12:25:07Z" title="2026-10-21T12:25:07Z" data-format="LL" data-datetime="calendar">21 oktober 2026 12:25</time></span>
        <span>Gepubliceerd <time datetime="2026-10-21T11:14:54Z" title="2026-10-21T11:14:54Z" data-format="LL" data-datetime="calendar">21 oktober 2026 11:14</time></span>
        <span data-reading-time>Leestijd wordt berekend…</span>
        
        
      </div>
      

      <div class="article-body" data-article-body><div data-test-id="guide-markup-preview">
<h2 id="h_01M5F1GKVR509PN21ER0S89HEC"><strong>Jouw veiligheid gaat voor</strong></h2>
<div style="background-color: #f7f2fd; border-radius: 8px; border: 2px solid #6a2fad; margin-bottom: 18px; padding: 18px 22px;">
<p style="font-size: 1.15em; margin-top: 0;"><strong>Jouw veiligheid gaat voor.</strong></p>
<p>Daarom zijn onze websites en die van onze klanten tijdelijk offline.<br><br>Er is een ernstig beveiligingslek ontdekt in PHP, een technologie die wereldwijd door miljoenen websites wordt gebruikt. Dit kan grote risico's opleveren voor de veiligheid van websites en gegevens.</p>
<p>Bij Mijndomein nemen we geen enkel onnodig risico als het gaat om de veiligheid van onze klanten. Daarom hebben we besloten om uit voorzorg onze eigen website en de websites die wij hosten tijdelijk offline te halen. <strong>We begrijpen dat dit vervelend is, maar veiligheid gaat voor bereikbaarheid. Altijd.</strong></p>
<p>Zodra de beveiligingsupdate beschikbaar is, gaan onze specialisten direct aan de slag om deze door te voeren en alle websites zo snel mogelijk weer veilig online te brengen.</p>
<p>We houden jullie op de hoogte via deze pagina.</p>
<p>Bedankt voor je begrip en geduld.</p>
<p style="margin-bottom: 0;"><strong>Team Mijndomein</strong></p>
</div>
<hr>
<h2 id="h_01M5F59M0JB5Q9PVSX6CN6JYK4"><strong>Huidige Status</strong></h2>
<ul>
<li data-list-item-id="e71b9ce
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
45 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

45
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
C
CDN & Delivery
Action
Assets on Cloudflare (host static.zdassets.com, 5 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host static.zdassets.com, 5 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (static.zdassets.com, 5 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a4e047500c33cfac-SJC
Info::
Assets on Cloudflare: static.zdassets.com (assets: 5), cache HIT
Got: cf-ray: a4e047500c33cfac-SJC
Info::
Assets on Cloudflare: mijndomein.zendesk.com (assets: 3), cache HIT
Got: cf-ray: a4e047501e9fcf13-SJC
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • static.zdassets.com — Cloudflare · assets: 5 · Cache Status: HIT
  • mijndomein.zendesk.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • www.googletagmanager.com — assets: 3 · Google
  • consent.cookiebot.com — assets: 2 · below probe threshold
  • scripts.clarity.ms — assets: 1 · below probe threshold
  • www.clarity.ms — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
A+
DNS Records
1 A records, 15 ms lookup
PASS
1 A records, 15 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 194.213.127.31
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:448:4005::31
Info::
2 nameserver(s) configured
Got: nsn1.mijndomein.nl, nsn2.mijndomein.nl
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 15 ms
Got: 15 ms
A194.213.127.31
AAAA2a01:448:4005::31
CNAME—
NSnsn1.mijndomein.nl, nsn2.mijndomein.nl
MX
5 mx1.mijndomein.nl
6 mx2.mijndomein.nl
TXT
SPF v=spf1 a mx include:spf.mijndomeinhosting.nl ~all
CAALookup not available with standard resolver
Resolved in 15 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+
Multi-Resolver DNS Speed
Mean 13ms across 3 resolvers (spread 11ms)
PASS
Mean 13ms across 3 resolvers (spread 11ms)
Info::
Cloudflare: 7ms
Got: 7ms via 1.1.1.1:53
Info::
Quad9: 15ms
Got: 15ms via 9.9.9.9:53
Info::
Google: 18ms
Got: 18ms via 8.8.8.8:53
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

302https://www.biermetstijl.com/
200https://biermetstijl.com/

Preferred variant: non-www

HTTP → HTTPS

301http://biermetstijl.com/ → https://biermetstijl.com/

Consistent

A
Domain Intelligence
biermetstijl.com — via Metaregistrar BV, 9 years, 11 months old, hosted on METAREGISTRAR - Metaregistrar B.V., NL
PASS
biermetstijl.com — via Metaregistrar BV, 9 years, 11 months old, hosted on METAREGISTRAR - Metaregistrar B.V., NL
Warning::
Domain expires in 75 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jan 4, 2027
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Metaregistrar BV
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.
Info::
Hosting: METAREGISTRAR - Metaregistrar B.V., NL
Got: AS42585
Domain expiry

75 days

January 4, 2027

SSL certificate

45 days

Issued by Let's Encrypt

Domain age

9 years, 11 months

Registered January 4, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

METAREGISTRAR - Metaregistrar B.V., NL

ASN AS42585

194.213.127.31

Registrar

Metaregistrar BV

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Metaregistrar BV
Created January 4, 2017 (9 years, 11 months ago)
Expires January 4, 2027 (2 months)
Last Updated January 5, 2026
Name Servers nsn1.mijndomein.nl, nsn2.mijndomein.nl
DNSSEC Not enabled
Hosting
IP Address 194.213.127.31
ASN AS42585 (METAREGISTRAR - Metaregistrar B.V., NL)
Provider METAREGISTRAR - Metaregistrar B.V., NL
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 460 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
21 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
144 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
148 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
461 ms
Total Time Total request time from DNS lookup through full response.
461 ms

Connection waterfall

DNS Lookup 21 ms TCP Connect 144 ms TLS Handshake 148 ms Server Processing 148 ms Content Transfer 0 ms
A+
Operational Status Page
Status page detected via anchor text
PASS
Status page detected via anchor text
Info::
Status page link found: https://mijndomein.zendesk.com/#
Got: https://mijndomein.zendesk.com/#
A+
Health Check Endpoint
Health endpoint at https://biermetstijl.com/health (HTTP 200)
PASS
Health endpoint at https://biermetstijl.com/health (HTTP 200)
Info::
Public health endpoint at https://biermetstijl.com/health
Got: https://biermetstijl.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback