Alternatives to fixpart.be
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
fixpart.be is registered with Name: team.blue nl B.V. and is hosted on AS20857 Signet B.V. in Netherlands. Its SSL certificate from Let's Encrypt expired on 30 Jan 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.
30 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| foxpart.xyz | Typo | 5 Oct 2026 | Checking… | Report → |
| fixart.pl | Typo | 5 Aug 2026 | Checking… | Report → |
| fixcart.xyz | Typo | 8 Oct 2026 | Checking… | Report → |
| fixeart.com | Typo | 7 Oct 2026 | Checking… | Report → |
| fixport.app | Typo | 7 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is fixpart.be’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Belgium | 78.6% | — | — | — |
| France | 8.7% | — | — | — |
| Netherlands | 6.2% | — | — | — |
| Guadeloupe | 2.6% | — | — | — |
| French Guiana | 1.2% | — | — | — |
Every IP address fixpart.be resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| fixpart.be | 85.10.138.99 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| fixpart.be | 2a01:7c8:bb0b:2db::1337 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| fixpart.be | 1 ASPMX.L.GOOGLE.com | 300 |
| fixpart.be | 5 ALT1.ASPMX.L.GOOGLE.com | 300 |
| fixpart.be | 5 ALT2.ASPMX.L.GOOGLE.com | 300 |
| fixpart.be | 10 ASPMX2.GOOGLEMAIL.com | 300 |
| fixpart.be | 10 ASPMX3.GOOGLEMAIL.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| fixpart.be | ns0.transip.net | 21600 |
| fixpart.be | ns1.transip.nl | 21600 |
| fixpart.be | ns2.transip.eu | 21600 |
| Host | Text | TTL |
|---|---|---|
| fixpart.be | "google-site-verification=mdBdTxjwfVLdfPIzreR8gvdRvOQygjFlxezyD8TAzJw" | 3600 |
| fixpart.be | "v=spf1 include:_spf.google.com include:_spf.fixpart.com include:sendgrid.net ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| fixpart.be | ns0.transip.net hostmaster.transip.nl 2023061500 86400 1800 2419200 300 | 3600 |
| Host | Value | TTL |
|---|---|---|
| fixpart.be | 256 3 13 JDeHs401sCL8sO/FGCenjp7rgLtsxn2U5QzO3Ro2ukI2iSCmnv7mAtLIgKebsdxMb2JpAu/FWA4KuE0w4u3frw== | 300 |
| fixpart.be | 257 3 13 omKgSiMDO7mJ+VeXE8vwi78+uWlErRTuBRi6Up+UmGoVnmTX+zAemaBTTbS9dsRm1PnlOWN5Y3CfNyPv19NUHQ== | 300 |
Other domains served from 85.10.138.99. Normal for shared hosting and CDNs.
No reviews yet. Used fixpart.be? 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.
fixpart.be has no community safety rating yet. Its SSL certificate expired on 30 Jan 2024. See Security →
fixpart.be is registered through Name: team.blue nl B.V. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
fixpart.be is served from 1 IP address, mainly on AS20857 Signet B.V. in Netherlands. See Hosting →
Raw registry data for fixpart.be. May be redacted by privacy services.
% .be Whois Server 6.1 % % The WHOIS service offered by DNS Belgium and the access to the records in the DNS Belgium % WHOIS database are provided for information purposes only. It allows % persons to check whether a specific domain name is still available or not % and to obtain information related to the registration records of % existing domain names. % % DNS Belgium cannot, under any circumstances, be held liable where the stored % information would prove to be incomplete or inaccurate in any sense. % % By submitting a query you agree not to use the information made available % to: % - allow, enable or otherwise support the transmission of unsolicited, % commercial advertising or other solicitations whether via email or otherwise; % - target advertising in any possible way; % - to cause nuisance in any possible way to the domain name holders by sending % messages to them (whether by automated, electronic processes capable of % enabling high volumes or other possible means). % % Without prejudice to the above, it is explicitly forbidden to extract, copy % and/or use or re-utilise in any form and by any means (electronically or % not) the whole or a quantitatively or qualitatively substantial part % of the contents of the WHOIS database without prior and explicit permission % by DNS Belgium, nor in any attempt thereof, to apply automated, electronic % processes to DNS Belgium (or its systems). % % You agree that any reproduction and/or transmission of data for commercial % purposes will always be considered as the extraction of a substantial % part of the content of the WHOIS database. % % By submitting the query you agree to abide by this policy and accept that % DNS Belgium can take measures to limit the use of its whois services in order to % protect the privacy of its registrants or the integrity of the database. % Domain: fixpart.be Status: NOT AVAILABLE Registered: Tue Jul 7 2015 Registrant: Not shown, please visit www.dnsbelgium.be for webbased whois. Registrar Technical Contacts: Registrar: Name: team.blue nl B.V. Website: https://www.transip.nl/ Nameservers: ns0.transip.net ns1.transip.nl ns2.transip.eu Keys: Flags: Please visit www.dnsbelgium.be for more info.
The first response from http://www.fixpart.be, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with fixpart.be. 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.