chapters.paris was registered with OVH on 1 Jun 2023 and is hosted on AS29222 Infomaniak Network SA in Switzerland. Its SSL certificate from Let's Encrypt expired on 21 Jun 2025, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
715 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| chapter5.xyz | Look-alike characters | 11 Oct 2026 | Checking… | Report → |
| chapter5.com | Look-alike characters | 23 Aug 2026 | Checking… | Report → |
| chapters.world | Other extension | 3 Nov 2026 | Checking… | Report → |
| chapters.coach | Other extension | 25 Oct 2026 | Checking… | Report → |
| chapters.forum | Other extension | 24 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is chapters.paris’s name taken on other extensions?
Every IP address chapters.paris resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| chapters.paris | 83.166.133.18 | 3599 |
| Host | Mail server | TTL |
|---|---|---|
| chapters.paris | 1 aspmx.l.google.com | 3600 |
| chapters.paris | 5 alt1.aspmx.l.google.com | 3600 |
| chapters.paris | 5 alt2.aspmx.l.google.com | 3600 |
| chapters.paris | 10 alt3.aspmx.l.google.com | 3600 |
| chapters.paris | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| chapters.paris | dns200.anycast.me | 3600 |
| chapters.paris | ns200.anycast.me | 3600 |
| Host | Text | TTL |
|---|---|---|
| chapters.paris | "google-site-verification=M0P6gwJH6_jqo7jhK8pyP3ycN0monfodeN_Wrqev3Uc" | 600 |
| chapters.paris | "v=spf1 include:_spf.google.com ~all" | 600 |
| Host | Start of authority | TTL |
|---|---|---|
| chapters.paris | dns200.anycast.me tech.ovh.net 2025050900 86400 3600 3600000 60 | 3600 |
| Host | Value | TTL |
|---|---|---|
| chapters.paris | 256 3 8 AwEAAaak4Jn7XB0bjc0TrQRIaaKDhaBbQ0+ylajWpdsN/f7DhLL+uOtyOPrmrNppjXKuniFi8MehwqkhrFW0Do44UbTqq3iEZHp4IdR4aoXZGL2Q+a4eWa08+5w17FtyWJNt7U7wTnTqx4yIkK5pUhcXnFqY4Kb+U/4mXdO5Sl8m8fRh | 3600 |
| chapters.paris | 257 3 8 AwEAAdNWDiAApkS0A1aMRiVC0ttUS9Jyf8cX23Q+xO9QHFw/Gb5UOe8P4VjRClQJPnV3eY1vJHhxu1Mmh4O3S++yRGSUgboRKleezZk38PDkUfRisTyppwpvopkvZ0uA9W/7sRayAqXqY+Hexswz7fSNmA5Ps46H9+NJyvXR4Ej3uJq1WpoHXJ8ZL0za86MZeYQo4fiwCAQ6djvYAOJ6DaqpNyhor+d2x7Tfc2IxeqFsAb2pmymTEvEz4eK5k2amp1HMLH8+cs5uYmo+vgs7fi7kSb1s7gRL8x/kMhu3Plbw0XF8+ei16nkF1b5A/gKrVW8cnRBMiM68YILeBZBrD79zO/8= | 3600 |
Other domains served from 83.166.133.18. Normal for shared hosting and CDNs.
No reviews yet. Used chapters.paris? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
chapters.paris has no community safety rating yet. Its SSL certificate expired on 21 Jun 2025. See Security →
chapters.paris is registered through OVH. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 1 Jun 2025. See Overview →
chapters.paris was registered on 1 Jun 2023, making it 3 years old. See Overview →
chapters.paris is served from 1 IP address, mainly on AS29222 Infomaniak Network SA in Switzerland. See Hosting →
Raw registry data for chapters.paris. May be redacted by privacy services.
Domain Name: chapters.paris Registry Domain ID: DOM6756044-PARIS Registrar WHOIS Server: whois.ovh.com Registrar URL: http://www.ovh.com Updated Date: 2025-04-28T18:46:26.54305Z Creation Date: 2023-06-01T16:25:19.747321Z Registry Expiry Date: 2025-06-01T16:25:19.731618Z Registrar: OVH Registrar IANA ID: 433 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +33.972101007 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Registry Registrant ID: REDACTED_FOR_PRIVACY Registrant Name: REDACTED_FOR_PRIVACY Registrant Organization: Sake Paris Registrant Contact Status: associated Registrant Contact Status: active Registrant Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Registrant City: REDACTED_FOR_PRIVACY Registrant Postal Code: REDACTED_FOR_PRIVACY Registrant State/Province: REDACTED_FOR_PRIVACY Registrant Country: REDACTED_FOR_PRIVACY Registrant Phone: REDACTED_FOR_PRIVACY Registrant Fax: REDACTED_FOR_PRIVACY Registrant Email: REDACTED_FOR_PRIVACY Registry Admin ID: REDACTED_FOR_PRIVACY Admin Name: REDACTED_FOR_PRIVACY Admin Organization: Sake Paris Admin Contact Status: associated Admin Contact Status: active Admin Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Admin City: REDACTED_FOR_PRIVACY Admin Postal Code: REDACTED_FOR_PRIVACY Admin State/Province: REDACTED_FOR_PRIVACY Admin Country: REDACTED_FOR_PRIVACY Admin Phone: REDACTED_FOR_PRIVACY Admin Fax: REDACTED_FOR_PRIVACY Admin Email: REDACTED_FOR_PRIVACY Registry Tech ID: REDACTED_FOR_PRIVACY Tech Name: REDACTED_FOR_PRIVACY Tech Organization: Sake Paris Tech Contact Status: associated Tech Contact Status: active Tech Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Tech City: REDACTED_FOR_PRIVACY Tech Postal Code: REDACTED_FOR_PRIVACY Tech State/Province: REDACTED_FOR_PRIVACY Tech Country: REDACTED_FOR_PRIVACY Tech Phone: REDACTED_FOR_PRIVACY Tech Fax: REDACTED_FOR_PRIVACY Tech Email: REDACTED_FOR_PRIVACY Registry Billing ID: REDACTED_FOR_PRIVACY Billing Name: REDACTED_FOR_PRIVACY Billing Organization: Sake Paris Billing Contact Status: associated Billing Contact Status: active Billing Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Billing City: REDACTED_FOR_PRIVACY Billing Postal Code: REDACTED_FOR_PRIVACY Billing State/Province: REDACTED_FOR_PRIVACY Billing Country: REDACTED_FOR_PRIVACY Billing Phone: REDACTED_FOR_PRIVACY Billing Fax: REDACTED_FOR_PRIVACY Billing Email: REDACTED_FOR_PRIVACY Name Server: dns200.anycast.me Name Server: ns200.anycast.me DNSSEC: signedDelegation URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2025-05-12T11:19:14.201323Z <<< For more information on Whois status codes, please visit https://icann.org/epp Rights restricted by copyright. If you wish to access the protected data, please visit our website at the following address: www.bienvenue.paris Terms of Use : City of Paris's database is protected by the provisions of the French Law of the 1st of July 1998 transposing the European Directive of the 11th of March 1996 on database legal protection in the Intellectual Property Code. City of Paris is the only entity to hold the producing rights of the databases as substantial investment, quantitative as much as qualitative, that were used to achieve this database. Complete or partial reproduction and/or use of City of Paris's database without the express permission of City of Paris is strictly forbidden. Any breach to these rules can carry penal sanctions as counterfeit, without prejudice of a potential damages request from City of Paris, holder of these rights. City of Paris's database user commits to use the published data according to the laws and rules in effect. Moreover, the user is bound to respect the French Data Protection Law. The infringement of the French Data Protection Law can carry penal sanctions. As the user will access personal information, the user must refrain from collecting or misuse this information. In a more general way, the user must refrain from any act likely to infringe the privacy or reputation of individuals.
The first response from http://www.chapters.paris, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with chapters.paris. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.