Alternatives to boots.no
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
boots.no was registered on 29 Sept 2014 and is hosted on AS19551 Incapsula Inc in United States of America. We couldn't read an SSL certificate for it when we last analysed it. WOT's community rates its safety good (74/100).
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.
We couldn't read an SSL certificate on port 443 when we last analysed boots.no. Refresh the analysis to check again.
2,525 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| boost.tools | Typo | 12 Nov 2026 | Checking… | Report → |
| boots.photography | Other extension | 11 Nov 2026 | Checking… | Report → |
| boots.homes | Other extension | 3 Nov 2026 | Checking… | Report → |
| boost.pics | Typo | 2 Nov 2026 | Checking… | Report → |
| obots.net | Typo | 30 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is boots.no’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Norway | 96.4% | — | — | — |
| Netherlands | 0.8% | — | — | — |
| Sweden | 0.7% | — | — | — |
| Finland | 0.5% | — | — | — |
| United States | 0.4% | — | — | — |
Every IP address boots.no resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| boots.no | 45.60.13.206 | 3581 |
| boots.no | 45.60.19.206 | 3581 |
| Host | Mail server | TTL |
|---|---|---|
| boots.no | 10 mxa-00320f01.gslb.pphosted.com | 300 |
| boots.no | 10 mxb-00320f01.gslb.pphosted.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| boots.no | ns1.netnames.net | 86400 |
| boots.no | ns2.netnames.net | 86400 |
| boots.no | ns5.netnames.net | 86400 |
| boots.no | ns6.netnames.net | 86400 |
| Host | Text | TTL |
|---|---|---|
| boots.no | "464779608d1b4ef49563609809c12864" | 86400 |
| boots.no | "7rt4y8sx7t933strm7dgg1npcm14s2k9" | 86400 |
| boots.no | "8lqv12dsl9mt95pqyg3fhrqy2nsrxnch" | 86400 |
| boots.no | "9b3eedvlrhi254m4nr9emna4pn" | 86400 |
| boots.no | "a9lvrojj03sronnm2s63g5qilk" | 86400 |
| boots.no | "bA9LOvVXjk8diat8OuPI21Wt80EqOpQqIOdmOFa7LLgHVA4Ra0XONZMJaCV0sroBzG07p27maADXj8Dxaa5d1g==" | 86400 |
| boots.no | "cd6004a0140a4a7884fe3f6e5cc1c42a" | 21600 |
| boots.no | "gy8gjd73mm66m9pc44sf9gk4thbhtksx" | 86400 |
| boots.no | "k0b2r7hu94mrquvkat3pucgesa" | 86400 |
| boots.no | "knowbe4-site-verification=c86ca28ccd7b15fcc528b85a1c9a879b" | 86400 |
| boots.no | "m1bctns64h5eng87hd8qsfvf10" | 86400 |
| boots.no | "MS=ms47567525" | 21600 |
| boots.no | "MS=ms69753682" | 300 |
| boots.no | "srcgocqm8m6cros3pkg0fc139g" | 86400 |
| boots.no | "u7ap7scvenu1mh5hsh4a06g6q9" | 86400 |
| boots.no | "v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all" | 300 |
| Host | Policy | TTL |
|---|---|---|
| boots.no | 0 issue buypass.no | 86400 |
| boots.no | 0 issue digicert.com | 86400 |
| boots.no | 0 issue godaddy.com | 86400 |
| boots.no | 0 issue letsencrypt.org | 86400 |
| boots.no | 0 issue sectigo.com | 86400 |
| boots.no | 0 issuewild godaddy.com | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| boots.no | ns1.netnames.net hostmaster.cscdns.net 2018072994 10800 1800 3600000 86400 | 21600 |
No reviews yet. Used boots.no? 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.
WOT's community rates boots.no good for safety (74/100). We couldn't read an SSL certificate on it when we last analysed it. See Security →
boots.no was registered on 29 Sept 2014, making it 12 years old. See Overview →
boots.no is served from 2 IP addresses, mainly on AS19551 Incapsula Inc in United States of America. See Hosting →
Raw registry data for boots.no. May be redacted by privacy services.
% By looking up information in the domain registration directory % service, you confirm that you accept the terms and conditions of the % service: % https://www.norid.no/en/domeneoppslag/vilkar/ % % Norid AS holds the copyright to the lookup service, content, % layout and the underlying collections of information used in the % service (cf. the Act on Intellectual Property of May 2, 1961, No. % 2). Any commercial use of information from the service, including % targeted marketing, is prohibited. Using information from the domain % registration directory service in violation of the terms and % conditions may result in legal prosecution. % % The whois service at port 43 is intended to contribute to resolving % technical problems where individual domains threaten the % functionality, security and stability of other domains or the % internet as an infrastructure. It does not give any information % about who the holder of a domain is. To find information about a % domain holder, please visit our website: % https://www.norid.no/en/domeneoppslag/ Domain Information NORID Handle...............: BOO859D-NORID Domain Name................: boots.no Registrar Handle...........: REG830-NORID Tech-c Handle..............: DA5529R-NORID Name Server Handle.........: NSNE3784H-NORID Name Server Handle.........: NSNE3785H-NORID Name Server Handle.........: NSNE3786H-NORID Name Server Handle.........: NSNE3787H-NORID Additional information: Created: 2014-09-29 Last updated: 2022-09-29<br><br>Information Updated: 2023-07-05 16:06:59
The first response from http://www.boots.no, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with boots.no. 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.