bol.com blocks automated analysis, answering with HTTP 403 to an automated client instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.
This site blocks automated analysis.
It answered our request with HTTP 403 to an automated client rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.
How does bol.com compare with other domains analysed here?
Measured against the 13 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 69% of them (median 353ms) |
|---|---|
| Domain age | Older than 64% of them |
Related domains in this index
Other domains analysed in this index:
When was bol.com registered?
bol.com was registered on 19 December 1997, which makes it about 28 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is Nom-iq Ltd. dba COM LAUDE.
Registration runs until 18 December 2026.
The domain carries 3 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 19 December 1997 |
|---|---|
| Expires | 18 December 2026 |
| Registrar | Nom-iq Ltd. dba COM LAUDE |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited |
Where is bol.com hosted?
The first address resolves to infrastructure in Utrecht, The Netherlands.
The network is operated by bol.com BV (AS396982 Google LLC).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is bol.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of bol.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 403 over
HTTPS.
At 178ms to first byte this response is fast for a homepage measured from a single European location.
At 12KB the HTML is unusually small, which typically means the page builds itself client-side after load.
No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.
| Server header | AkamaiNetStorage |
|---|---|
| Compression | none |
| Page size | 12,569 bytes |
| Declared language | not declared |
| Mobile viewport | not declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is bol.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-28, which is 54 days from the date of this check. It covers
1 hostname.
- bol.com
The certificate has 54 days left to run.
It covers 1 hostname, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
| Header | Set | Value |
|---|
How is DNS configured for bol.com?
| IP addresses | 79.170.100.62 |
|---|---|
| Reverse DNS | 79.170.100.62 |
| Name servers | ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c4.googledomains.com, ns-cloud-c1.googledomains.com |
| Mail (MX) | pro-mail-mx-003.bol.com (pri 10), pro-mail-mx-004.bol.com (pri 10) |
| SPF | v=spf1 ip4:185.14.169.192/27 ip4:185.14.168.192/27 ip4:185.14.168.0/27 ip4:185.14.171.64/28 ip4:185.14.171.80/28 ip4:185.14.168.64/27 ip4:91.194.0.0/26 include:spf1.bol.com include:spf.protection.outlook.com -all |
| TXT records | 21 |
bol.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 2 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 79.170.100.62, which usually names the hosting provider.
Can bol.com be spoofed in email?
DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.
CAA records restrict certificate issuance to 6 named authorities (issue thawte.com, issue globalsign.com, issue geotrust.com, issuewild digicert.com), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 6,805 bytes and names
7 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.bol.com/sitemap/nl-nl/
- https://www.bol.com/sitemap/nl-be/
- https://www.bol.com/sitemap/fr-be/
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does bol.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own bol.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026.
Analyse another domain →
