neckermann.be Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of neckermann.be on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 3139ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 136 KB.
Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted.
The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, 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 2 technologies across 2 categories powering neckermann.be. The detected stack includes Google Tag Manager and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, neckermann.be receives an overall trust score of 65/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time3139ms
ProtocolHTTP/2
Page Size136 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
ServerKestrel
Total Requests232
3rd Party Domains3
Redirect1 hop(s)
Detected Technologies (2)
🏷️ Google Tag Manager
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✓
Strict-Transport-Security (HSTS)
Set ✓
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=YR2
SubjectcommonName=neckermann.be
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
neckermann.be Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, neckermann.be receives a trust score of 65/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification.
Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved.
We checked neckermann.be 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.
Trust Signals
✅ Valid HTTPS
✅ HSTS enabled
✅ SPF configured
✅ DMARC configured (p=none)
✅ DKIM configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
neckermann.be Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned neckermann.be and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for neckermann.be.
Icon Set: Font Awesome — provides additional functionality for neckermann.be.
We also extracted the following tracking identifiers: Google Tag Manager container GTM-PL8J64W. These IDs can be used to identify other websites operated by the same organization.
Tag Manager
🏷️ Google Tag Manager(95%)
Icon Set
Tracking IDs
neckermann.be Performance, Speed & Core Web Vitals
🤖 AI Summary
neckermann.be delivers its homepage in 3139ms (server response time), which is considered slow by industry standards. The total page weight is 136 KB, and we detected 232 resource requests loading assets from 3 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.
The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections.
Asset minification status: 0 out of 3 CSS files and 0 out of 11 JavaScript files are minified. Minifying the remaining 14 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 neckermann.be produces approximately 0.07g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 136 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for neckermann.be. 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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.07g
RatingA
Page Weight & Optimization
HTML Size136 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests232
3rd Party Domains3
CSS Minified0/3
JS Minified0/11
neckermann.be DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
neckermann.be resolves to the IPv4 address 35.186.229.134, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured.
The domain name system is managed by 4 name servers: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, and ns-cloud-d4.googledomains.com. Having 4 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 neckermann.be is handled by Microsoft 365 with 1 MX records configured: neckermann-be.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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit.
DNSSEC is not enabled for neckermann.be. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.
Our subdomain enumeration scan discovered 2 active subdomains for neckermann.be: m.neckermann.be and www.neckermann.be. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns-cloud-d1.googledomains.com
ns-cloud-d2.googledomains.com
ns-cloud-d3.googledomains.com
ns-cloud-d4.googledomains.com
MX
neckermann-be.mail.protection.outlook.com
Email & Authentication
MX ProviderMicrosoft 365
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (2 found)
m.neckermann.be www.neckermann.be
neckermann.be Page Content, Images & Accessibility
🤖 AI Summary
The homepage of neckermann.be contains 789 words of visible text content. This is a moderate amount of content. The page is structured with 7 H2 headings, 8 H3 headings, 0 H4 headings, 0 H5, and 8 H6 headings.
The page includes 22 images. 18 images (82%) 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 18% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 155 internal links pointing to other pages on the same domain and 4 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 11 external JavaScript files, 3 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), Schema.org structured data (ImageObject, OpeningHoursSpecification, PostalAddress, and TravelAgency), and Progressive Web App (PWA) manifest (enabling app-like installation).
Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility.
The website has social media presence across 2 platforms: Facebook (@neckermann.be) and Instagram (@neckermann_belgie). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1Vind hier je hemelse vakantie
H2 Tags7
H3 Tags8
H4 Tags0
H5 Tags0
H6 Tags8
Internal Links155
External Links4
Assets & Features
JavaScript Files11
JS Minified0/11
CSS Files3
CSS Minified0/3
Iframes0
Images22
Missing Alt18
SitemapYes ✓
Robots.txtNo
PWAYes ✓
AMPNo
RSS FeedNo
Schema.org Types
ImageObjectOpeningHoursSpecificationPostalAddressTravelAgency
Social Media Presence
Facebook: @neckermann.beInstagram: @neckermann_belgie
neckermann.be SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for neckermann.be is too long at 75 characters: "Neckermann - Ga nu op last minute vliegvakantie tot -40% tijdelijk verlaagd". At 75 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning.
The meta description is 164 characters (slightly long): "Ruim aanbod aan type vakanties! Last minutes, vliegvakantie, autovakantie, exotische vakanties, citytrips. Vind hier je ...". 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://neckermann.be/nl, preventing duplicate content issues, the page language is declared as nl-be, and a favicon is configured.
No Open Graph tags are configured. When someone shares a link to neckermann.be on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.
The site implements Schema.org structured data with the following types: ImageObject, OpeningHoursSpecification, PostalAddress, and TravelAgency. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.
Google SERP Preview
Neckermann - Ga nu op last minute vliegvakantie tot -40% tijdelijk verlaagd
https://neckermann.be
Ruim aanbod aan type vakanties! Last minutes, vliegvakantie, autovakantie, exotische vakanties, citytrips. Vind hier je Neckermann Travel Shop (reisbureau) dichtbij
Meta Tags
TitleNeckermann - Ga nu op last minute vliegvakantie tot -40% tij...
Title Length75 chars
Meta Desc Length164 chars
H1Vind hier je hemelse vakantie
Languagenl-BE
Canonicalhttps://neckermann.be/nl
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema TypesImageObject, OpeningHoursSpecification, PostalAddress, TravelAgency
OG Type—
OG ImageNot set
Twitter Card—
FaviconSet ✓