jemontremesseins.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 32 days left18 years oldTranco #92808
60
jemontremesseins.com was registered on 13 Sep 2008 via OVH sas and the registry expiry is 13 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/jemontremesseins.com.
jemontremesseins.com publishes 2 nameservers. DNSSEC is not signed.
jemontremesseins.com has 1 IPv4 address (188.165.44.175). The geolocation database places 188.165.44.175 in Roubaix, France.
The TLS certificate from YR2 is valid and has 32 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, Materialize CSS, Nginx, cdnjs and jQuery. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
jemontremesseins.com was registered on 13 Sep 2008 via OVH sas. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/jemontremesseins.com.
| Registered | since 13 Sep 2008 |
|---|---|
| Created | 13 September 2008 |
| Updated | 14 September 2026 |
| Expires | 13 September 2027 |
| Registrar | OVH sas |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | dns11.ovh.net, ns11.ovh.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/jemontremesseins.com |
jemontremesseins.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
jemontremesseins.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver dns11.ovh.net is published for jemontremesseins.com in the registration record from https://rdap.verisign.com/com/v1/domain/jemontremesseins.com.
Nameserver ns11.ovh.net is published for jemontremesseins.com in the registration record from https://rdap.verisign.com/com/v1/domain/jemontremesseins.com.
DNS
jemontremesseins.com has 1 address record, 7 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.165.44.175 |
|---|---|
| AAAA | — |
| NS | dns11.ovh.net, ns11.ovh.net |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, aspmx2.googlemail.com (10) Google, aspmx3.googlemail.com (10) Google, aspmx4.googlemail.com (10) Google, aspmx5.googlemail.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at jemontremesseins.com is "v=spf1 a mx ip4:188.165.44.175 include:_spf.google.com include:sendgrid.net include:mail.zendesk.com include:sim.dplads.com ~all".
The DMARC text record at _dmarc.jemontremesseins.com is "v=DMARC1;p=none;pct=100;rua=mailto:[email protected];ruf=mailto:[email protected];ri=86400;aspf=r;adkim=r;fo=1;".
IPv4 address 188.165.44.175 answers for jemontremesseins.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 10. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 10. The host is recognised as Google.
Mail exchanger aspmx4.googlemail.com has preference 10. The host is recognised as Google.
Mail exchanger aspmx5.googlemail.com has preference 10. The host is recognised as Google.
Hosting and geo
jemontremesseins.com is placed in Roubaix, France by the local geolocation database (db-ip).
| Address | 188.165.44.175 |
|---|---|
| Country | France |
| City | Roubaix |
| Source | db-ip |
SSL/TLS
The certificate for jemontremesseins.com is valid, with 32 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | jemontremesseins.com |
| Valid from | 4 September 2026 |
| Valid until | 3 December 2026 |
| Days left | 32 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: jemontremesseins.com, www.jemontremesseins.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- Materialize CSS · UI frameworks
- Nginx · Web servers, Reverse proxies
- cdnjs · CDN
- jQuery · JavaScript libraries
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
Materialize CSS is filed under UI frameworks.
Nginx is filed under Web servers, Reverse proxies.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 13 ms. The target title is 61 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 13 ms |
| Title length | 61 no |
| Quoted title | "Je Montre Mes Seins : vos gros seins ou petits seins en photo" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | fr |
| Links | 126 |
| Images | 91 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for jemontremesseins.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for jemontremesseins.com. That resolver covers adult and malware names.
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Roubaix.
- October 2026: geo country changed from empty to France.
Questions
Is jemontremesseins.com safe?
Cloudflare family DNS returned a block for jemontremesseins.com. That resolver covers adult and malware names.
Who hosts jemontremesseins.com?
jemontremesseins.com is placed in Roubaix, France.
When does jemontremesseins.com expire?
jemontremesseins.com expires on 13 September 2027 according to https://rdap.verisign.com/com/v1/domain/jemontremesseins.com.
Who owns jemontremesseins.com?
The registry did not return a person or a company for jemontremesseins.com. RDAP often redacts the registrant. The registrar on file is OVH sas.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/jemontremesseins.com at 2026-10-30T13:59:56Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:59:56Z
- TLS source tls:443 at 2026-10-30T13:59:56Z
- HTTP source https://jemontremesseins.com/ at 2026-10-30T13:59:56Z
- Tech source wappalyzergo at 2026-10-30T13:59:56Z
- Geo source db-ip at 2026-10-30T13:59:56Z
- Safety source family DNS and local lists at 2026-10-30T13:59:56Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.