jan.berlin was registered with Gandi SAS on 25 Jul 2019 and is hosted on AS16509 in United States. Its SSL certificate from Amazon is valid until 4 Mar 2027, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
2 of 5 protections set up
Lists the servers allowed to send email for this domain.
v=spf1 include:_spf.google.com ~allSigns outgoing mail so receivers can verify it.
selector google._domainkeyPolicy is “reject”, but for only 1% of mail.
v=DMARC1; p=reject; pct=1; rua=mailto:[email protected],mailto:[email protected];Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
811 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| jari.computer | Look-alike characters | 1 Nov 2026 | Checking… | Report → |
| j4n.tattoo | Look-alike characters | 19 Oct 2026 | Checking… | Report → |
| jari.si | Look-alike characters | 11 Oct 2026 | Checking… | Report → |
| jari.wedding | Look-alike characters | 17 Sept 2026 | Checking… | Report → |
| jari.gg | Look-alike characters | 22 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is jan.berlin’s name taken on other extensions?
Every IP address jan.berlin resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| jan.berlin | 3.167.192.108 | 60 |
| jan.berlin | 3.167.192.18 | 60 |
| jan.berlin | 3.167.192.2 | 60 |
| jan.berlin | 3.167.192.53 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| jan.berlin | 1 aspmx.l.google.com | 3600 |
| jan.berlin | 5 alt1.aspmx.l.google.com | 3600 |
| jan.berlin | 5 alt2.aspmx.l.google.com | 3600 |
| jan.berlin | 10 alt3.aspmx.l.google.com | 3600 |
| jan.berlin | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| jan.berlin | ns-1114.awsdns-11.org | 172800 |
| jan.berlin | ns-1696.awsdns-20.co.uk | 172800 |
| jan.berlin | ns-323.awsdns-40.com | 172800 |
| jan.berlin | ns-814.awsdns-37.net | 172800 |
| Host | Text | TTL |
|---|---|---|
| jan.berlin | "google-site-verification=_El-qkLlPUPP171kY4HBgsL76dyf01tK2dk8n7jYlZg" | 3600 |
| jan.berlin | "v=spf1 include:_spf.google.com ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| jan.berlin | ns-814.awsdns-37.net awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 13.32.241.120. Normal for shared hosting and CDNs.
No reviews yet. Used jan.berlin? 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.
jan.berlin has no community safety rating yet. Its SSL certificate is valid until 4 Mar 2027. See Security →
jan.berlin is registered through Gandi SAS. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expires on 25 Jul 2027 — in 8 months. See Overview →
jan.berlin was registered on 25 Jul 2019, making it 7 years old. See Overview →
jan.berlin is served from 4 IP addresses, mainly on AS16509 in United States. See Hosting →
Raw registry data for jan.berlin. May be redacted by privacy services.
Domain Name: jan.berlin Registry Domain ID: D0000485311-BERLIN Registrar WHOIS Server: whois.gandi.net Registrar URL: http://www.gandi.net/ Updated Date: 2026-06-20T06:31:58Z Creation Date: 2019-07-25T06:24:32Z Registry Expiry Date: 2027-07-25T06:24:32Z Registrar: Gandi SAS Registrar IANA ID: 81 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +33.170377661 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: ns-1114.awsdns-11.org Name Server: ns-1696.awsdns-20.co.uk Name Server: ns-323.awsdns-40.com Name Server: ns-814.awsdns-37.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of Whois database: 2026-11-05T17:25:29Z <<< For more information on Whois status codes, please visit https://icann.org/epp % Copyright (c) 2026 by dotBERLIN GmbH & Co. KG % % Except for agreed Internet operational purposes, % no part of this information may be reproduced, % stored in a retrieval system, or transmitted, % in any form or by any means, electronic, mechanical, % recording, or otherwise, without prior permission % of dotBERLIN GmbH & Co. KG on behalf of itself % and/or the copyright holders. Any use of this % material to target advertising or similar activities % is explicitly forbidden and can be prosecuted. % % Furthermore, it is strictly forbidden to use the % Whois database in such a way that jeopardizes or % could jeopardize the stability of the technical systems % of dotBERLIN GmbH & Co. KG under any circumstances. % In particular, this includes any misuse of the % Whois database and any use of the Whois database % which disturbs its operation. % % Should the user violate these points, % dotBERLIN GmbH & Co. KG reserves the right % to deactivate the Whois database entirely or % partly for the user. Moreover, the user shall % be held liable for any and all damage arising % from a violation of these points. % % For privacy reasons, personal data are not disclosed. % You may request this data under strict conditions by completing % a personal data disclosure form at www.whois.berlin.
The first response from http://www.jan.berlin, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with jan.berlin. 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.
No changes seen since we started recording on 5 Nov 2026.