pecheur.com — domain analysis
pecheur.com describes itself as "Pecheur.com, spécialiste de la vente d". It was registered in 1999, served from Toronto, Canada. It has a valid HTTPS certificate, 4 of 6 common security headers.
What is pecheur.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:
- pecheur ×19
- alma ×17
- avec ×14
- pour ×10
- prix ×9
- paiement ×9
- client ×8
- public ×8
- conseill ×8
- achats ×8
Does pecheur.com publish the usual trust pages?
None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does pecheur.com compare with other domains analysed here?
Measured against the 77 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 66% of them (median 662ms) |
|---|---|
| Security headers | More than 89% of them |
| Domain age | Older than 79% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was pecheur.com registered?
pecheur.com was registered on 3 February 1999, which makes it about 27 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 Gandi SAS.
Registration runs until 3 February 2036.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 3 February 1999 |
|---|---|
| Expires | 3 February 2036 |
| Registrar | Gandi SAS |
| Registry status | client transfer prohibited |
Where is pecheur.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).
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 pecheur.com running on?
pecheur.com exposes 1 identifiable technology: Cloudflare.
Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.
- Cloudflare
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 511ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 163KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 166,840 bytes |
| Declared language | fr |
| Mobile viewport | declared |
What does the homepage say about itself?
The title runs to 77 characters, so search results will truncate it and the end of the sentence will not be read.
A meta description of 38 characters is present.
12 of 49 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.
| Title | Pecheur.com boutique & magasin de peche en ligne pour les passionnés de pêche (77 chars) |
|---|---|
| Meta description | Pecheur.com, spécialiste de la vente d (38 chars) |
| H1 | Pecheur.com, vente d’articles de pêche et de navigation (1 on the page) |
| Canonical | https://www.pecheur.com/ |
| Open Graph title | not set |
| Headings / images | 7 H2s, 49 images (12 without alt text) |
Is pecheur.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-15, which is 70 days from the date of this check. It covers
2 hostnames.
- pecheur.com
- *.pecheur.com
The certificate has 70 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
4 of 6 are set (HSTS, Content Security Policy, X-Content-Type-Options, Referrer-Policy). Absent: X-Frame-Options, Permissions-Policy.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000; includeSubDomains;preload |
| Content Security Policy | yes | frame-ancestors https://www.chasseur.com; |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | no | — |
| Referrer-Policy | yes | same-origin, strict-origin-when-cross-origin |
| Permissions-Policy | no | — |
How is DNS configured for pecheur.com?
| IP addresses | 104.18.16.86, 104.18.17.86, 2606:4700::6812:1056, 2606:4700::6812:1156 |
|---|---|
| Reverse DNS | 104.18.16.86, 104.18.17.86 |
| Name servers | ns-57-b.gandi.net, ns-57-a.gandi.net, ns-71-c.gandi.net |
| Mail (MX) | ASPMX.L.GOOGLE.com (pri 1), ALT1.ASPMX.L.GOOGLE.com (pri 5), ALT2.ASPMX.L.GOOGLE.com (pri 5), ALT4.ASPMX.L.GOOGLE.com (pri 10), ALT3.ASPMX.L.GOOGLE.com (pri 10) |
| SPF | v=spf1 ip4:185.62.41.169 ip4:185.62.40.48 include:_spf.google.com include:spf.mailjet.com include:mail.zendesk.com ~all |
| TXT records | 6 |
pecheur.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 5 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 104.18.16.86, 104.18.17.86, which usually names the hosting provider.
Who runs DNS and mail for pecheur.com?
Mail is handled by Google Workspace.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about pecheur.com?
4 of 4 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.
1 email address appears in the homepage markup, where address-harvesting crawlers will find it.
Can pecheur.com be spoofed in email?
DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.
No CAA records are published, so any certificate authority may issue a certificate 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 3,468 bytes and names
2 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.pecheur.com/sitemap-news-post.xml.gz
- https://www.pecheur.com/sitemap-index.xml
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?
- Organization
- ContactPoint
- AggregateRating
- Review
- Person
- Rating
- OnlineStore
The homepage publishes 7 structured data types: Organization, ContactPoint, AggregateRating, Review, Person, Rating, OnlineStore.
What does pecheur.com load from third parties?
The homepage pulls resources from 2 third-party hosts (files.webyn.ai, i.ytimg.com). Each one sees the visitor IP and user agent on every page load.
1 cookie is set before any interaction (RP_HTTP_PECHEUR_COM).
The page links or refers to X/Twitter, Facebook, Instagram, YouTube.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| RP_HTTP_PECHEUR_COM | yes | yes | none/unset |
Does pecheur.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both pecheur.com and www.pecheur.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 pecheur.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does pecheur.com run?
No analytics or advertising trackers were detected on the homepage of pecheur.com, which is unusual for a commercial site.
How does pecheur.com look when shared?
1 of 5 social preview tags are set. Missing: og:title, og:description, og:type, twitter:card.
The page declares 20 hreflang alternates (fr-fr, de-de, de-at, nl-be, fr-be, da-dk, es-es, fi-fi, el-gr, en-ie, it-it, nl-nl), so it targets more than one language or region.
How are images, fonts and scripts handled?
49 images on the homepage, 8 of them lazy-loaded (16%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 4 external stylesheets and 4 external scripts, with 2 carrying defer or async.
Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.
Is pecheur.com accessible and current?
The page uses 3 landmark elements and 25 ARIA attributes.
There are 15 form inputs but only 11 label elements, so some fields may be unlabelled for screen readers.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
The visible copyright notice reads 2004, 22 years behind the current year, which usually indicates the site is not actively maintained.
Can search engines index pecheur.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 287 internal and 7 external links across 7 outside hosts.
Visible text makes up 8% of the HTML.
The heading outline skips 1 level, which breaks the document structure screen readers navigate by.
How is pecheur.com delivered?
The HTML is served with Cache-Control: private, no-store.
Frequently asked questions
Does pecheur.com set the usual HTTP security headers?
It sets 4 of 6. The ones not present are: X-Frame-Options, Permissions-Policy.
Does pecheur.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 pecheur.com built with?
The homepage exposes these fingerprints: Cloudflare. 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 pecheur.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 →
The weekly edition
Three or four things explained, in plain language, with the sources. One email a week. No spam, no algorithm in between.
