rd.nl

We performed a comprehensive analysis of rd.nl on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 31499ms. The page is served over HTTP/2 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 634 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-08-09, which is 41 days from now. The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 4 technologies across 4 categories powering rd.nl. The detected stack includes Nuxt.js, React, Vite, and Google Tag Manager. The site uses Nuxt.js as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, rd.nl receives an overall trust score of 79/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, rd.nl receives a trust score of 79/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 41 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked rd.nl against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned rd.nl and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Nuxt.js — provides the application framework and routing for rd.nl. UI Library: React — handles the user interface rendering and component management for rd.nl. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for rd.nl. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for rd.nl. We also extracted the following tracking identifiers: Google Tag Manager container GTM-PM6MGL3. These IDs can be used to identify other websites operated by the same organization.

rd.nl delivers its homepage in 31499ms (server response time), which is considered slow by industry standards. The total page weight is 634 KB, and we detected 313 resource requests loading assets from 17 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. No compression is currently enabled on rd.nl. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 9 CSS files and 0 out of 2 JavaScript files are minified. Minifying the remaining 11 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of rd.nl produces approximately 0.31g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 634 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for rd.nl. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

rd.nl resolves to the IPv4 address 188.166.135.27 and also supports IPv6 (2a03:b0c0:2:f0::f9d1:f001), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 3 name servers: ns0.transip.net, ns1.transip.nl, and ns2.transip.eu. Having 3 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for rd.nl is handled by Microsoft 365 with 1 MX records configured: rd-nl.mail.protection.outlook.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for rd.nl, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.

The homepage of rd.nl contains 2,204 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 55 H2 headings, 52 H3 headings, 0 H4 headings. The page includes 93 images. 11 images (12%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 88% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 119 internal links pointing to other pages on the same domain and 36 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 2 external JavaScript files, 9 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), Progressive Web App (PWA) manifest (enabling app-like installation), and RSS feed for content syndication. Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 4 platforms: Facebook (@refdag), Twitter (@refdag), Instagram (@rdbeeld), and Linkedin (@reformatorischdagblad). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for rd.nl is good at 69 characters: "Reformatorisch Dagblad | Laatste christelijke nieuws en achtergronden". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 114 characters (well-optimized): "Nieuws, kerkelijke actualiteit, achtergronden en opinie vanuit christelijk oogpunt. | Lees RD drie maanden gratis.". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://www.rd.nl/, preventing duplicate content issues, the page language is declared as nl, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Home..."), OG description, OG image (social sharing thumbnail), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.