<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">TypoAlert: a browser extension against typosquatting</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Francesco</forename><surname>Blefari</surname></persName>
							<email>francesco.blefari@unical.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Calabria</orgName>
								<address>
									<settlement>Rende</settlement>
									<region>CS</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">IMT Schools for Advanced Studies</orgName>
								<address>
									<settlement>Lucca (LU)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Angelo</forename><surname>Furfaro</surname></persName>
							<email>angelo.furfaro@unical.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Calabria</orgName>
								<address>
									<settlement>Rende</settlement>
									<region>CS</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Giovambattista</forename><surname>Ianni</surname></persName>
							<email>ianni@unical.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Calabria</orgName>
								<address>
									<settlement>Rende</settlement>
									<region>CS</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Alessandro</forename><surname>Viscomi</surname></persName>
							<email>a.viscomi00@gmail.com</email>
						</author>
						<title level="a" type="main">TypoAlert: a browser extension against typosquatting</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">2D8B216740F5E475803BC52BFCF2E41E</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:06+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>TypoSquatting</term>
					<term>URL Hijacking</term>
					<term>Privacy</term>
					<term>Phishing</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Nowadays, web browsing has become ubiquitous, with virtually everyone navigating the internet and routinely entering website addresses. However, frequent typing can lead to errors, resulting in the inadvertent input of incorrect domain names. One prevalent risk stemming from such mistakes is known as typosquatting, where users inadvertently land on maliciously crafted websites due to minor typing errors. By exploiting typographical errors made by users, typosquatting represents a malicious tactic wherein attackers capitalize on such mistakes to redirect unwitting victims to entirely different or deceptively similar websites. While various techniques and tools have been developed to mitigate this threat, currently, there is a notable absence of user-friendly tools available to everyday web users. This paper describes TypoAlert, a Chrome-based extension engineered to address this gap in defense against typosquatting. TypoAlert is meticulously crafted to analyze, detect, and promptly alert users in real-time about the legitimacy of the web domains they are visiting.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>In the current panorama of digital threats, cybersquatting represents an illicit activity aimed to hijack domain names that correspond to trademarks or famous personalities. Over time, this threat has evolved into the phenomenon known as typosquatting: a threat based on typing errors made by users when entering a URL into their browser. The attackers, called (typosquatters), register domains that contain spelling errors compared to legitimate domains, taking advantage of people's inevitable oversights. This kind of attack is particularly effective when the reference domain is frequently visited because even a small percentage of user typing errors generates a significant flow of traffic to typosquatted sites.</p><p>Typosquatted sites are web sites whose domain name are similar to legitimate domain name, and can host a wide range of content aimed to generate profits through advertising and often containing malicious elements and/or redirects to malicious websites. Usually, the attackers exploit typosquatted sites to conduct attack campaigns, such as phishing, or even to steal sensitive user information. Prior research <ref type="bibr" target="#b0">[1]</ref> indicates that a considerable percentage, ranging from 10% to 20%, of manually entered URLs contain errors. For instance, an average user who erroneously inputs the URL of a popular website has a 1 out of 14 probability of landing on a typosquatted domain <ref type="bibr" target="#b0">[1]</ref>. The consequences of typosquatting are profound and far-reaching. Companies suffer not only from traffic declines but also from subsequent financial losses, while users remain persistently vulnerable to potential online scams. Despite the wealth of studies conducted in this domain <ref type="bibr" target="#b1">[2]</ref>, and the presentation of several prototype anti-typosquatting tools in the past, there exists a lack of practical and effective solutions available to the general public, particularly those offering real-time assistance to users. This paper presents the TypoAlert extension for chrome-based browsers and shows how combining multiple anti-typosquatting methods into an integrated framework is possible in order to implement an effective detection tool against typosquatting. Remarkably, as our methods are not machine learning-based, they do not require cycles of training on input datasets; thus the maintenance effort of TypoAlert is reduced to the bare minimum. Moreover, we assessed the effectiveness of TypoAlert on an appropriate set of domain names. Section 2 summarizes some previous studies on typosquatting and highlighting the necessary background information. Section 3 briefly presents our typosquatting detection methodology and illustrates the experimental results obtained during the evaluation and validation phase. Section 4 presents the chrome-based extension, its features and how it works. Section 5 draws the conclusions and indicates some future research directions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Background and related work</head><p>The general term cyber-typosquatting might refer not just to domain name typosquatting but also to package typosquatting <ref type="bibr" target="#b2">[3]</ref> and to other forms of typosquatting, like exploitation of typing errors in mobile app names, social media names, etc. Typosquatting remains a widespread and persistent practice, primarily due to the lack of effective solutions to prevent it <ref type="bibr" target="#b0">[1]</ref>. Research on the topic can be roughly categorized in: (i) general analyses; (ii) company-centric antityposquatting proposals; and, (iii) user-centric anti-typosquatting research.</p><p>General studies. The study presented in <ref type="bibr" target="#b3">[4]</ref> identified over 8800 registered domains within typographic variations compared to popular domain names and more than 90% of these redirected to sexually explicit content often designed to make it hard to shut down the offending content.</p><p>Initially, it was believed that shorter URLs were more susceptible to typosquatting <ref type="bibr" target="#b4">[5]</ref>, however, <ref type="bibr" target="#b5">[6]</ref> indicated that domains with longer names share a similar probability of being subject to typosquatting.</p><p>Similarly, the popularity of domain names was originally seen as a factor related to typosquatting <ref type="bibr" target="#b4">[5]</ref>. This assumption has also been revisited; indeed, a shift in typosquatters' behavior has been identified in <ref type="bibr" target="#b6">[7]</ref>: around 95% of typosquatted domains now targets lesser popular domains.</p><p>During the years, various models for generating typosquatted domains have been proposed. Five primary models have been identified <ref type="bibr" target="#b7">[8]</ref>: Missing-dot typos, Character-omission typos, Character-permutation typos, Character-substitution typos, and Character-duplication typos. A subsequent study <ref type="bibr" target="#b8">[9]</ref> scrutinizes registered domains whose name has been generated according to each of the five described models, evaluating their saturation. This work also provided valuable insights into the level of awareness regarding various typo domain generation models among distinct online entities. As shown in <ref type="bibr" target="#b8">[9]</ref>, both malicious and defensive registrations mirror the saturation trends. This implies that both attackers and defenders share a similar perception regarding the typosquatted domains deemed worthy of registration.</p><p>Existing models were extended by introducing additional approaches in <ref type="bibr" target="#b9">[10]</ref>. These include: (i) 1-mod-inplace: involves in replacing all domain name characters, one at a time, with every possible letter of the alphabet; (ii) 1-mod-deflate: entails removing, one at a time, all characters from the domain name; (iii) 1-mod-inflate: involves adding a character to the domain name, systematically considering all possible characters.</p><p>All these generation models are based on the Levenshtein distance (also known as edit distance) <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b11">12]</ref>. This metric allows to quantify the similarity between two strings, and is thus a crucial parameter for evaluating the similarity of typo domains to the original domain. However, when considering the character permutation generation model, the more appropriate reference is the Damerau-Levenshtein distance <ref type="bibr" target="#b12">[13]</ref> which differs from plain Levenshtein distance by incorporating the operation of transposition between characters, in addition to insertion, deletion, and substitution operations. In <ref type="bibr" target="#b1">[2]</ref> it is highlighted that 99% of typosquatted sites exhibit a Damerau-Levenshtein distance of one from their target domains.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Company and user-centric anti-typosquatting tools.</head><p>The pioneer Strider Typo-Patrol tool <ref type="bibr" target="#b7">[8]</ref> is meant for discovering large typosquatting campaigns. It employed a multifaceted approach, incorporating (i) a Typo-Neighborhood Generator to produce sets of URLs with potential typos, (ii) a Typo-Neighborhood Scanner to actively analyze domains and record information such as third-party URLs and page content, and (iii) a Domain-Parking Analyzer for in-depth analysis of typosquatted domains. The same work proposed Strider URL Tracer, an instrument meant to allow website owners to monitor typosquatted domains targeting their sites. A comprehensive and relatively recent analysis of typosquatting domain registrations within the .com TLD can be found in <ref type="bibr" target="#b6">[7]</ref>. The analysis was conducted using the Yet Another Typosquatting Tool (YATT).</p><p>Another approach was provided in the now defunct iTrustPage Firefox extension <ref type="bibr" target="#b13">[14]</ref>, which provided automated identification of legitimate web pages, utilizing user input and external sources such as search engine results, including whitelists and local caches. A browser extension called The Anti Typosquatting Tool (ATST) was proposed in <ref type="bibr" target="#b0">[1]</ref>. It provided several features such as: (i) a User Customized Local Repository for monitoring popular domains, (ii) an Edit-distance Computation Module employing the Damerau-Levenshtein distance for typosquatted domain checks, and (iii) a User Customized Local Repository Update Module for dynamic updates based on user interactions. The Stop URL Typo-squatting (SUT) approach, proposed in <ref type="bibr" target="#b4">[5]</ref>, addresses the broader issue of detecting phony websites, whose domain name is not necessarily typosquatted. This solution integrates autonomous modules for: (i) network-level criteria that assesses URL features (called SUT-net module) (ii) and site popularity assessment that leverages Google search results to evaluate domain legitimacy (called SUT-pop module).</p><p>Another tool that is also worth mentioning is TypoWriter <ref type="bibr" target="#b14">[15]</ref>, which anticipates most likely domain variations using Recurrent Neural Networks trained on DNS logs. Unfortunately, at the time of writing, all the above mentioned tools are no longer available on the web.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Detection Methodology</head><p>Behind our developed Chrome-based extension there is a detection algorithm that aims to classify the type of the web domain at hand. Our tool aims to integrate several anti-typosquatting techniques and to provide real-time monitoring, detection and filtering software. We also included additional detection features meant identifying as detection of domain names which are registered, yet are not used and/or intended for bad uses called parked domains. The detection process starts taking in input a domain name 𝑛 and, after analysis, 𝑛 is classified. The output is one of the following categories: NotTypo (𝑛 is not a typosquat), ProbablyNotTypo, ProbablyTypo, Typo, ProbablyTypoPhishing, TypoPhishing, TypoMalware, and is built according to a score (av, alert value) and to the value of a phishing indicator (ph) which are both obtained as outcomes of the evaluation step.</p><p>A pre-filtering step is achieved by considering two lists: a blacklist (BL) and a whitelist (WL). The blacklist leverages the BlackBook list, an historical (black)list of malicious domains created as part of the periodic automated heuristic check (i.e. WHOIS, HTTP, etc.) of newly reported entries from public lists of malicious URLs <ref type="bibr" target="#b15">[16]</ref>. The BlackBook blacklist is used to check whether the domain at hand is considered malware; if so, the domain is marked as a 𝑇 𝑦𝑝𝑜𝑀 𝑎𝑙𝑤𝑎𝑟𝑒 domain.</p><p>Let vd be the domain name eventually reached from 𝑛 after following a potential chain of redirects. If 𝑛 ∈ 𝑊 𝐿 or vd ∈ 𝑊 𝐿, we give to 𝑛 the minimum alert value, i.e. 0, classifying it as NotTypo. The WL list is constructed using a Top Domain Repository (TDR), giving at the same time the capability of adding more domains using the User Domain Repository (UDR); this latter can be populated directly by using the web page related to the developed extension. The WL is a list that can be reasonably assumed to be reliable and authentic built considering the top domains provided by Data4Seo <ref type="bibr" target="#b16">[17]</ref>. Data4Seo website allows to export data concerning the top 1000 national web domains for each of the 74 distinct nations available and also the 1000 web domains with the highest ranking worldwide. We added to 𝑊 𝐿 all top domains present on Data4Seo website (for a total of around 32000 distinct domain names) and the user added trusted domains. TDR cannot be modified by the user, which can however customize the complementary UDR, which is initially empty.</p><p>Afterwards, we build a set 𝐶𝑇 of candidate targets. 𝐶𝑇 is built by considering each element having DL-distance equals to 1 from 𝑛 taken from: (i) 𝑊 𝐿, (ii) the top 10 domain names resulting by querying a search engine with 𝑛 as the search keyword and whenever available, (iii) the domain name dym ("Did you mean?" domain), i.e. the domain name suggested by the search engine at hand as the inferred correct search keyword.</p><p>Once the 𝐶𝑇 list is built, the evaluation step starts by computing the Parking Alert (PARKA) indicator which is set to either 0 or 1 according to an analysis based on a set of keyphrases, in different speaking languages, usually present in parked web pages. Then for each element 𝑐𝑡 ∈ 𝐶𝑇 we evaluate the Top 10 Alert (T10A) indicator, the Did You Mean Alert (DYMA) indicator and the Phishing Alert (PHA) indicator.</p><p>The T10A indicator considers the result list obtained by querying the input domain 𝑛 on a search engine; we compute the T10A 𝑐𝑡 score. This indicator returns: (i) 1 if 𝑛 is present in the resulting list; (ii) -1 if 𝑛 is not present in the resulting list; (iii) 0 in all other cases.</p><p>The DYMA indicator is based on the concept of domain popularity, and it exploits the suggested Last but not least, there is the PHA 𝑐𝑡 indicator that evaluates the similarity degree between the web page related to the input domain 𝑛 and the web page related to 𝑐𝑡. This evaluation is carried out using fuzzy hashing <ref type="bibr" target="#b17">[18]</ref> and returns the score value 0 or 1.</p><p>Based on the above indicators, the alert value 𝑎𝑣 is computed as follows:</p><formula xml:id="formula_0">𝑎𝑣 = ⎧ ⎨ ⎩ 0 if 𝑛 ∈ WL 7 if 𝑛 ∈ BL 2 + PARKA + 𝑎𝑣 |𝐶𝑇 otherwise</formula><p>where</p><formula xml:id="formula_1">𝑎𝑣 |𝐶𝑇 = max 𝑐𝑡∈𝐶𝑇 {(T10A 𝑐𝑡 + DYMA 𝑐𝑡 + PHA 𝑐𝑡 )}.</formula><p>Along with 𝑎𝑣 we obtain the phishing alert (𝑝ℎ) value as PHA 𝑐𝑡 * where 𝑐𝑡 * is one of the arguments for which 𝑎𝑣 |𝐶𝑇 is reached and for which PHA is maximal, i.e.</p><formula xml:id="formula_2">𝑐𝑡 * = 𝑎𝑟𝑔 max 𝑐𝑡∈𝐶𝑇 {PHA(𝑐𝑡)|T10A 𝑐𝑡 + DYMA 𝑐𝑡 + PHA 𝑐𝑡 = 𝑎𝑣 |𝐶𝑇 }.</formula><p>Finally, in the last step (see Figure <ref type="figure" target="#fig_0">1</ref>) we label 𝑛 according to 𝑎𝑣 and 𝑝ℎ: for 𝑎𝑣 = 0, we assign the label 𝑁 𝑜𝑡𝑇 𝑦𝑝𝑜; for 𝑎𝑣 = 1, we assign the label 𝑃 𝑟𝑜𝑏𝑎𝑏𝑙𝑦𝑁 𝑜𝑡𝑇 𝑦𝑝𝑜; for 𝑎𝑣 = 2 we assign either the label 𝑃 𝑟𝑜𝑏𝑎𝑏𝑙𝑦𝑇 𝑦𝑝𝑜 or 𝑃 𝑟𝑜𝑏𝑎𝑏𝑙𝑦𝑇 𝑦𝑝𝑜𝑃 ℎ𝑖𝑠ℎ𝑖𝑛𝑔 depending on the value of 𝑝ℎ, respectively if 0 or 1; for 𝑎𝑣 = 7 we assign the label 𝑇 𝑦𝑝𝑜𝑀 𝑎𝑙𝑤𝑎𝑟𝑒 while for any value 𝑎𝑣 ∈ <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b5">6]</ref> we assign either 𝑇 𝑦𝑝𝑜𝑃 ℎ𝑖𝑠ℎ𝑖𝑛𝑔 if 𝑝ℎ = 1 or 𝑇 𝑦𝑝𝑜 if 𝑝ℎ = 0.</p><p>To assess the effectiveness of the classification techniques which TypoAlert is based on, we conducted an evaluation utilizing a purposely constructed dataset, named 𝑇 𝑆, including a set  of potential typosquatted domains. To build the ground truth, each domain 𝑑 ∈ 𝑇 𝑆 has been manually analyzed and classified as being or not a typosquatted domain. Then we compared the results with the outcomes achieved by our classifier.</p><p>To build the 𝑇 𝑆 dataset we started from the set 𝑇 𝑜𝑝, comprising the top 1000 websites globally ranked on Google, as per DataForSEO <ref type="bibr" target="#b16">[17]</ref>. We extracted a subset of 300 domains by uniformly sampling 𝑇 𝑜𝑝 and using the open source tool ail-typo-squatting <ref type="bibr" target="#b18">[19]</ref>, we built a set containing all domain names having a Damerau-Levenshtein distance from 𝑑's name which is equal to 1. Then we extracted a subset of all domain names 𝑑 such that (i) 𝑑 was actually registered in a DNS at the time of construction of the dataset; and (ii) there was an active web server responding (directly or indirectly) to HTTP(S) requests made to 𝑑. Finally, we obtained 𝑇 𝑆 . The final dataset TS includes potential 5106 typo domains.</p><p>During the evaluation phase we conducted an analysis on the tool accuracy and we compared it with ground truth obtained manually. During the manual classification we labelled domains as (i) Typo: designated for domains considered malicious; (ii) NotTypo: assigned to either a legitimate domain or a domain that redirects to the legitimate domain. Note that, to mitigate the role of human subjectivity in manual annotations, we opted for building binary ground truth values. However, since TypoAlert produces a score value between 0 and 7, data have been validated by mapping our scores to ground truth. We consider an aggregation threshold 𝑡, and we build a family of binary classifiers each denoted by the two classes 𝑁 𝑜𝑡𝑇 𝑦𝑝𝑜 𝑡 = {𝑥 ∈ 𝑇 𝑆 | 𝑠(𝑥) &lt; 𝑡}, and 𝑇 𝑦𝑝𝑜 𝑡 = 𝑇 𝑆 ∖ 𝑇 𝑦𝑝𝑜 𝑡 . We identified the classifier that maximizes the TPR/FPR Ratio (True positive rate divided by False Positive Rate), as the one obtained for 𝑡 = 2. The Receiver Operating Characteristic (ROC) curve shows the trade-off between True Positive Rate and False Positive Rate of each classifier built among various score thresholds, as depicted in Figure <ref type="figure" target="#fig_2">2a</ref>. Figure <ref type="figure" target="#fig_2">2b</ref> depicts the confusion matrix for 𝑡 = 2, where 5060 over 5106 domains with a 99.0% of domains were correctly classified.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">The extension</head><p>We took several design choices in developing TypoAlert. First things first, as our software would be a browser extension, we have chosen to support all Chrome-based browsers.</p><p>TypoAlert aims to improve the user experience in browsing the web without being pervasive for the users. To carry out this goal, TypoAlert, once installed in the browser, shows as the only visible additional feature, an icon in the dedicated extension section. This icon changes its color based on the web site present on the active tab. These colors have been chosen to give users a rapid evaluation measure of the domain kind they are visiting and may vary according to the Figure <ref type="figure" target="#fig_4">3</ref>  Different result values returned by analysis involve different (or none) alert notification. If the extension's analysis indicates a label among ProbablyTypo, Typo, TypoPhishing, Probablyty-poPhishing or TypoMalware (colors from yellow to dark red), an alert appears, warning the user about the detected severity level. When the analysis returns 𝑁 𝑜𝑡𝑇 𝑦𝑝𝑜 or 𝑃 𝑟𝑜𝑏𝑎𝑏𝑙𝑦𝑁 𝑜𝑡𝑇 𝑦𝑝𝑜 no alert is given and the user is allowed to visit the related web page, in this case the TypoAlert icon becomes either Green or Green-Yellow.</p><p>If a typosquatting attempt is detected, the extension's icon becomes red and an alert about the domain classification is shown. In Fig. <ref type="figure" target="#fig_6">4a</ref> it is depicted the alert that appears when the domain 𝑛 is a typo and it is visited for the first time. It was highlighted before that the Phishing Alert indicator evaluates if a web domain is malicious and aims to conduct a phishing attack. If the Phishing Alert indicates that a web domain is a possible phishing web domain, the user is notified using a specific pop-up alert highlighting this special kind (malicious) of the web domain. Moreover, we inserted in the extension a caching mechanism that helps in avoiding multiple evaluations about the same site. Domain names classified as typosquatted are retained in the extension cache. If a domain name 𝑏 has been classified as typosquatted in the last 30 days the web page of 𝑏 is blocked and replaced by a notification page as depicted in Fig. <ref type="figure" target="#fig_6">4b</ref>. Users can always access the extensions options and add misclassified domains to the verified user whitelist, excluding them from the analysis.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusions and future work</head><p>In this paper we presented TypoAlert, a tool for detecting typosquatted sites that, combining some of the known simplest yet provably effective practices, is able to detect a relevant number of  typosquatted domains. The validation phase proves the effectiveness of the approach. As future work, we are planning to enrich TypoAlert with features that tackle typosquatting from an even more user-centric perspective, in the spirit of dynamic skins <ref type="bibr" target="#b19">[20]</ref>. TypoAlert hase been released under LGPL license and it can be downloaded from https://github.com/aleviscomi/typoalert.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Labelling Algorithm</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2:</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head></head><label></label><figDesc>. Given a domain name 𝑛 the TypoAlert icon can assume a different color: (i) Blue: if the analysis is not started yet; (ii) Dark-Red: if 𝑛 is marked as TypoMalware or TypoPhishing; (iii) Red: 𝑛 is marked as Typo; (iv) Yellow: if 𝑛 is marked as ProbablyTypo or ProbablyTypoPhishing; (v) Green-Yellow: if 𝑛 is marked as ProbablyNotTypo; (vi) Green: if 𝑛 is marked as NotTypo.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Different colours of the toggle extension.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head></head><label></label><figDesc>(a) Alert popup for a typosquat domain (b) Notification page for a typosquat domain</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: TypoAlert notification.</figDesc><graphic coords="8,92.68,87.39,180.00,117.36" type="bitmap" /></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>This work was partially supported by projects SERICS (PE00000014) and FAIR (PE0000013) under the MUR National Recovery and Resilience Plan funded by the European Union -NextGenera-tionEU.</p></div>
			</div>


			<div type="funding">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>A. Viscomi) https://blefari.xyz/ (F. Blefari); https://angelo.furfaro.dimes.unical.it/ (A. Furfaro); https://www.mat.unical.it/ianni/ (G. Ianni) 0009-0000-2625-631X (F. Blefari); 0000-0003-2537-8918 (A. Furfaro); 0000-0003-0534-6425 (G. Ianni)</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Combating typo-squatting for safer browsing</title>
		<author>
			<persName><forename type="first">G</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">F</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">R</forename><surname>Marupally</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">K</forename><surname>Singireddy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Yin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Paruchuri</surname></persName>
		</author>
		<idno type="DOI">10.1109/WAINA.2009.98</idno>
	</analytic>
	<monogr>
		<title level="m">2009 International Conference on Advanced Information Networking and Applications Workshops</title>
				<imprint>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="31" to="36" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">The landscape of domain name typosquatting: Techniques and countermeasures</title>
		<author>
			<persName><forename type="first">J</forename><surname>Spaulding</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Upadhyaya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mohaisen</surname></persName>
		</author>
		<idno type="DOI">10.1109/ARES.2016.84</idno>
	</analytic>
	<monogr>
		<title level="m">2016 11th International Conference on Availability, Reliability and Security (ARES)</title>
				<imprint>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="284" to="289" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Defending against package typosquatting</title>
		<author>
			<persName><forename type="first">M</forename><surname>Taylor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Vaidya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Davidson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">De</forename><surname>Carli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Rastogi</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-65745-1_7</idno>
	</analytic>
	<monogr>
		<title level="m">Network and System Security: 14th International Conference, NSS 2020</title>
				<meeting><address><addrLine>Melbourne, VIC, Australia; Berlin, Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer-Verlag</publisher>
			<date type="published" when="2020">November 25-27, 2020. 2020</date>
			<biblScope unit="page" from="112" to="131" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">B</forename><surname>Edelman</surname></persName>
		</author>
		<ptr target="https://cyber.harvard.edu/archived_content/people/edelman/typo-domains/,2003" />
		<title level="m">Large-scale registration of domains with typographical errors</title>
				<imprint/>
		<respStmt>
			<orgName>Harvard University</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Sut: Quantifying and mitigating url typosquatting</title>
		<author>
			<persName><forename type="first">A</forename><surname>Banerjee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">S</forename><surname>Rahman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Faloutsos</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.comnet.2011.06.005</idno>
	</analytic>
	<monogr>
		<title level="j">Computer Networks</title>
		<imprint>
			<biblScope unit="volume">55</biblScope>
			<biblScope unit="page" from="3001" to="3014" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Measuring the Perpetrators and Funders of Typosquatting</title>
		<author>
			<persName><forename type="first">T</forename><surname>Moore</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Edelman</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-642-14577-3_15</idno>
		<imprint>
			<date type="published" when="2010">2010</date>
			<publisher>Springer</publisher>
			<biblScope unit="page" from="175" to="191" />
			<pubPlace>Berlin Heidelberg</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">The long &quot;Taile&quot; of typosquatting domain names</title>
		<author>
			<persName><forename type="first">J</forename><surname>Szurdi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Kocso</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Cseh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Spring</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Felegyhazi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Kanich</surname></persName>
		</author>
		<ptr target="https://www.usenix.org/conference/usenixsecurity14/technical-sessions/presentation/szurdi" />
	</analytic>
	<monogr>
		<title level="m">USENIX Security Symposium (USENIX Security 14)</title>
				<meeting><address><addrLine>San Diego, CA</addrLine></address></meeting>
		<imprint>
			<publisher>USENIX Association</publisher>
			<date type="published" when="2014">2014</date>
			<biblScope unit="page" from="191" to="206" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<author>
			<persName><forename type="first">Y.-M</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Beck</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Verbowski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Daniels</surname></persName>
		</author>
		<ptr target="https://www.usenix.org/conference/sruti-06/strider-typo-patrol-discovery-and-analysis-systematic-typo-squatting" />
		<title level="m">2nd Workshop on Steps to Reducing Unwanted Traffic on the Internet (SRUTI 06)</title>
				<meeting><address><addrLine>San Jose, CA</addrLine></address></meeting>
		<imprint>
			<publisher>USENIX Association</publisher>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page">6</biblScope>
		</imprint>
	</monogr>
	<note>Strider Typo-Patrol: Discovery and analysis of systematic Typo-Squatting</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Seven months&apos; worth of mistakes: A longitudinal study of typosquatting abuse</title>
		<author>
			<persName><forename type="first">P</forename><surname>Agten</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Joosen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Piessens</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Nikiforakis</surname></persName>
		</author>
		<idno type="DOI">10.14722/ndss.2015.23058</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings 2015 Network and Distributed System Security Symposium, NDSS 2015</title>
				<meeting>2015 Network and Distributed System Security Symposium, NDSS 2015</meeting>
		<imprint>
			<publisher>Internet Society</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page">13</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Cyber-fraud is one typo away</title>
		<author>
			<persName><forename type="first">A</forename><surname>Banerjee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Barman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Faloutsos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">N</forename><surname>Bhuyan</surname></persName>
		</author>
		<idno type="DOI">10.1109/INFOCOM.2008.258</idno>
	</analytic>
	<monogr>
		<title level="m">IEEE INFOCOM 2008 -The 27th Conference on Computer Communications</title>
				<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="1939" to="1947" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Binary codes capable of correcting deletions, insertions, and reversals</title>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">I</forename><surname>Levenshtein</surname></persName>
		</author>
		<ptr target="https://api.semanticscholar.org/CorpusID:60827152" />
	</analytic>
	<monogr>
		<title level="j">Soviet physics. Doklady</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="page" from="707" to="710" />
			<date type="published" when="1965">1965</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">A technique for computer detection and correction of spelling errors</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">J</forename><surname>Damerau</surname></persName>
		</author>
		<idno type="DOI">10.1145/363958.363994</idno>
	</analytic>
	<monogr>
		<title level="j">Commun. ACM</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="page" from="171" to="176" />
			<date type="published" when="1964">1964</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">A guided tour to approximate string matching</title>
		<author>
			<persName><forename type="first">G</forename><surname>Navarro</surname></persName>
		</author>
		<idno type="DOI">10.1145/375360.375365</idno>
	</analytic>
	<monogr>
		<title level="j">ACM Comput. Surv</title>
		<imprint>
			<biblScope unit="volume">33</biblScope>
			<biblScope unit="page" from="31" to="88" />
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Itrustpage: a user-assisted anti-phishing tool</title>
		<author>
			<persName><forename type="first">T</forename><surname>Ronda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Saroiu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Wolman</surname></persName>
		</author>
		<idno type="DOI">10.1145/1357010.1352620</idno>
	</analytic>
	<monogr>
		<title level="j">SIGOPS Oper. Syst. Rev</title>
		<imprint>
			<biblScope unit="volume">42</biblScope>
			<biblScope unit="page" from="261" to="272" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Typowriter: A tool to prevent typosquatting</title>
		<author>
			<persName><forename type="first">I</forename><surname>Ahmad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Parvez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Iqbal</surname></persName>
		</author>
		<idno type="DOI">10.1109/COMPSAC.2019.00068</idno>
	</analytic>
	<monogr>
		<title level="m">IEEE 43rd Annual Computer Software and Applications Conference (COMPSAC)</title>
				<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="423" to="432" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Stampar</surname></persName>
		</author>
		<ptr target="https://github.com/stamparm/blackbook" />
		<title level="m">Blackbook: a historical (black)list of malicious domains</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title/>
		<author>
			<persName><surname>Dataforseo</surname></persName>
		</author>
		<ptr target="https://dataforseo.com/free-seo-stats/top-1000-websites" />
		<imprint>
			<date type="published" when="1000">1000. 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<monogr>
		<title level="m" type="main">Approximate matching: definition and terminology</title>
		<author>
			<persName><forename type="first">F</forename><surname>Breitinger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Guttman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mccarrin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Roussev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>White</surname></persName>
		</author>
		<idno type="DOI">10.6028/nist.sp.800-168</idno>
		<imprint>
			<date type="published" when="2014">2014</date>
			<publisher>National Institute of Standards and Technology</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<ptr target="https://github.com/typosquatter/ail-typo-squatting,2023" />
		<title level="m">Ail-typo-squatting</title>
				<imprint/>
	</monogr>
	<note>AIL project</note>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">The battle against phishing: Dynamic security skins</title>
		<author>
			<persName><forename type="first">R</forename><surname>Dhamija</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">D</forename><surname>Tygar</surname></persName>
		</author>
		<idno type="DOI">10.1145/1073001.1073009</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 1st Symposium on Usable Privacy and Security, SOUPS 2005</title>
				<editor>
			<persName><forename type="first">L</forename><forename type="middle">F</forename><surname>Cranor</surname></persName>
		</editor>
		<meeting>the 1st Symposium on Usable Privacy and Security, SOUPS 2005<address><addrLine>Pittsburgh, Pennsylvania, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2005">July 6-8, 2005. 2005</date>
			<biblScope unit="volume">93</biblScope>
			<biblScope unit="page" from="77" to="88" />
		</imprint>
	</monogr>
	<note>ACM International Conference Proceeding Series</note>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
