reifen.com — domain analysis
AdvantageBizMarketing Editorial
October 5, 2026
·
0 min read
reifen.com describes itself as "Reifen & Felgen für PKWs, Motorräder & Transporter versandkostenfrei bei reifen.com ✔ Unschlagbare Preise ✔ Flexible Zahlung ✔ Montagepartner vor Ort". It was registered in 1996, served from Hamburg, Germany. It has a valid HTTPS certificate, 6 of 6 common security headers, 1 tracking script.
What is reifen.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- english ×6
- deutsch ×5
- fran ×3
- reifen ×2
- select ×2
- language ×2
- browser ×2
Does reifen.com publish the usual trust pages?
Found: about, terms. Not found at the usual addresses:
contact, privacy.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does reifen.com compare with other domains analysed here?
Measured against the 74 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 65% of them (median 486ms) |
|---|---|
| Security headers | More than 98% of them |
| Domain age | Older than 84% of them |
Related domains in this index
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was reifen.com registered?
reifen.com was registered on 16 July 1996, which makes it about 30 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 InterNetX GmbH.
Registration runs until 15 July 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 16 July 1996 |
|---|---|
| Expires | 15 July 2027 |
| Registrar | InterNetX GmbH |
| Registry status | client transfer prohibited |
Where is reifen.com hosted?
The first address resolves to infrastructure in Hamburg, Germany.
The network is operated by euNetworks GmbH (AS13237 euNetworks GmbH).
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 reifen.com running on?
reifen.com exposes 1 identifiable technology: Google Tag Manager.
Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.
- Google Tag Manager
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 233ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 19KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 19,830 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 29 characters, inside the range that displays without truncation.
A meta description of 150 characters is present.
No H1 heading was found, so the page offers no single top-level statement of what it is.
All 15 images on the homepage have alt attributes.
| Title | Reifen & Felgen | reifen.com (29 chars) |
|---|---|
| Meta description | Reifen & Felgen für PKWs, Motorräder & Transporter versandkostenfrei bei reifen.com ✔ Unschlagbare Preise ✔ Flexible Zahlung ✔ Montagepartner vor Ort (150 chars) |
| H1 | — none — (0 on the page) |
| Canonical | https://www.reifen.com |
| Open Graph title | not set |
| Headings / images | 0 H2s, 15 images (0 without alt text) |
Is reifen.com served over a valid certificate?
The HTTPS certificate is issued by Sectigo Limited and is
valid until 2027-02-10, which is 128 days from the date of this check. It covers
2 hostnames.
- *.reifen.com
- reifen.com
The certificate has 128 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
All 6 headers checked are set, which is uncommon and indicates someone configured them deliberately.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000; includeSubDomains |
| Content Security Policy | yes | default-src 'self'; connect-src *; font-src * data:; frame-src *; img-src * data:; media-src *; object-src *; script-src |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | yes | strict-origin |
| Permissions-Policy | yes | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=*, payment=*, usb=() |
How is DNS configured for reifen.com?
| IP addresses | 62.80.103.141, 62.80.103.143 |
|---|---|
| Reverse DNS | www.reifen.com, www.reifen.com |
| Name servers | c.ns14.net, b.ns14.net, ns1.reifen.com, d.ns14.net |
| Mail (MX) | de-smtp-inbound-2.mimecast.com (pri 10), mail.reifen.com (pri 20), de-smtp-inbound-1.mimecast.com (pri 10) |
| SPF | v=spf1 mx ip4:194.145.122.253 ip4:62.80.103.184 ip4:85.10.215.193 a:mail.reifen.com a:spf.couplingmail.com include:de._netblocks.mimecast.com include:spf.smtp.net include:spf.mailjet.com include:_spf.zimpel.de -all |
| TXT records | 4 |
reifen.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 3 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to www.reifen.com, www.reifen.com, which usually names the hosting provider.
Who runs DNS and mail for reifen.com?
Mail is handled by Mimecast.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about reifen.com?
3 of 3 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
Can reifen.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 6 named authorities (issue digicert.com, issuewild letsencrypt.org, issuewild sectigo.com, issue sectigo.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 175 bytes and names
1 user-agent group.
It does not blanket-disallow general crawlers.
No sitemap is declared in robots.txt.
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.
What does reifen.com load from third parties?
The homepage pulls resources from 6 third-party hosts (edge.optimeleon.com, googletagmanager.com, privacy-proxy.usercentrics.eu, rubbex.com, web.cmp.usercentrics.eu, y7fqc8isr6.kameleoon.eu). Each one sees the visitor IP and user agent on every page load.
7 cookies are set before any interaction (srv_b2c, .Nop.Customer, .Nop.NoRelocation, .Nop.NoRelocation, .Nop.Session). 4 lack the Secure flag.
The page links or refers to X/Twitter.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| srv_b2c | no | yes | lax |
| .Nop.Customer | no | no | none/unset |
| .Nop.NoRelocation | no | no | none/unset |
| .Nop.NoRelocation | yes | yes | none/unset |
| .Nop.Session | no | yes | lax |
| TS0124c467 | yes | yes | strict |
| TS019b3d1d | yes | yes | strict |
Does reifen.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both reifen.com and www.reifen.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can reifen.com be crawled?
A sitemap index is served at https://reifen.com/sitemap.xml listing 23 entries.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does reifen.com run?
1 tracking script detected: Google Tag Manager.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does reifen.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
The page declares 18 hreflang alternates (fr-BE, nl-BE, de-BE, en-BE, fr-LU, de-LU, en-LU, da-DK, en-DK, de-DE, en-DE, de-AT), so it targets more than one language or region.
How are images, fonts and scripts handled?
15 images on the homepage, 0 of them lazy-loaded (0%).
Modern image formats are in use (1 WebP/AVIF references).
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 9 external stylesheets and 8 external scripts, with 4 carrying defer or async.
Is reifen.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index reifen.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 9 internal and 13 external links across 5 outside hosts.
Visible text is only 2.5% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is reifen.com delivered?
The HTML is served with Cache-Control: no-cache,no-store.
Frequently asked questions
Does reifen.com set the usual HTTP security headers?
Yes — all 6 headers checked are present.
Does reifen.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is reifen.com built with?
The homepage exposes these fingerprints: Google Tag Manager. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 5 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 reifen.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 5 October 2026.
Analyse another domain →
AdvantageBizMarketing Editorial
SEO strategist and content editor at AdvantageBizMarketing.