Alternatives to bour.so
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
bour.so was registered with whois.nic.so on 28 Aug 1997 and is hosted on AS20675 Boursorama S.A. in France. Its SSL certificate from DigiCert Inc expired on 3 Aug 2024, 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.
295 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| boru.ltd | Typo | 12 Nov 2026 | Checking… | Report → |
| boru.fit | Typo | 11 Nov 2026 | Checking… | Report → |
| obur.xyz | Typo | 5 Nov 2026 | Checking… | Report → |
| boru.kz | Typo | 30 Oct 2026 | Checking… | Report → |
| boru.ie | Typo | 5 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is bour.so’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Guatemala | 40.4% | — | — | — |
| Ecuador | 20% | — | — | — |
| Italy | 14.9% | — | — | — |
| France | 13.4% | — | — | — |
| United Kingdom | 11.3% | — | — | — |
Every IP address bour.so resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| bour.so | 195.42.250.13 | 21600 |
| Host | Mail server | TTL |
|---|---|---|
| bour.so | 0 mail001.boursorama.fr | 300 |
| bour.so | 0 mail101.boursorama.fr | 300 |
| Host | Name server | TTL |
|---|---|---|
| bour.so | ns1.boursorama.com | 21600 |
| bour.so | ns2.boursorama.com | 21600 |
| bour.so | ns3.boursorama.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| bour.so | "79sj0jq3p82m1zbrcd7m12q4tv6j93wg" | 3600 |
| bour.so | "v=spf1 -all" | 3600 |
| Host | Policy | TTL |
|---|---|---|
| bour.so | 0 issue Digicert.com | 3600 |
| bour.so | 0 issue letsencrypt.org | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| bour.so | ns1.boursorama.com hostmaster.boursorama.fr 2022112201 21600 3600 604800 86400 | 21600 |
No reviews yet. Used bour.so? 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.
bour.so has no community safety rating yet. Its SSL certificate expired on 3 Aug 2024. See Security →
bour.so is registered through whois.nic.so. See WHOIS →
bour.so was registered on 28 Aug 1997, making it 29 years old. See Overview →
bour.so is served from 1 IP address, mainly on AS20675 Boursorama S.A. in France. See Hosting →
Raw registry data for bour.so. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: SO organisation: Ministry of Post and Telecommunications contact: administrative name: Administrator organisation: Ministry of Post and Telecommunications phone: +252 1 587 1200 fax-no: +252 1 231 599 e-mail: admin@mipt.gov.so contact: technical name: Tech Manager organisation: soNIC address: Via Republic address: Mogadishu Benadir 1000 address: Somalia phone: +252 61 8250888 fax-no: +252 61 8250991 e-mail: admin@sonic.gov.so nserver: D.NIC.SO 196.216.168.54 2001:43f8:120:0:0:0:0:54 nserver: E.NIC.SO 2001:500:14:6101:ad:0:0:1 204.61.216.101 whois: whois.nic.so status: ACTIVE remarks: Registration information: http://www.nic.so/ created: 1997-08-28 changed: 2016-04-18 source: IANA
The first response from http://www.bour.so, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with bour.so. 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.