Measure The Web

User Tools

Site Tools

Trace:
design:website_classification

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
design:website_classification [2025/01/02 17:44] – Figures in float (wrap) karelkubicekdesign:website_classification [2025/06/23 08:50] (current) – [Adult Websites, Security, and Privacy Protection] karelkubicek
Line 20: Line 20:
     - Limited granularity in labels, which may not suit detailed marketing or behavioral analysis.     - Limited granularity in labels, which may not suit detailed marketing or behavioral analysis.
     - Documentation includes deprecated categories, leading to potential misinterpretations.     - Documentation includes deprecated categories, leading to potential misinterpretations.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ==== FortiGuard ==== ==== FortiGuard ====
Line 30: Line 30:
     - Lower label granularity may restrict its applicability outside security domains.     - Lower label granularity may restrict its applicability outside security domains.
     - Limited documentation transparency in certain sensitive categories.     - Limited documentation transparency in certain sensitive categories.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ==== Symantec ==== ==== Symantec ====
Line 39: Line 39:
     - Taxonomy is less diverse compared to marketing-oriented services.     - Taxonomy is less diverse compared to marketing-oriented services.
     - Limited coverage for obscure or long-tail domains.     - Limited coverage for obscure or long-tail domains.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ==== Trend Micro ==== ==== Trend Micro ====
Line 46: Line 46:
     - Labels aligned with threat intelligence, enhancing usability in cybersecurity contexts.     - Labels aligned with threat intelligence, enhancing usability in cybersecurity contexts.
   * **Disadvantages**:   * **Disadvantages**:
-    - (TODO: URL, API)+    - <wrap todo>TODO: are there any?</wrap> 
 +  <wrap todo>TODO: URL, API</wrap>
  
 ==== Forcepoint ==== ==== Forcepoint ====
Line 55: Line 56:
     - Limited multi-labeling capabilities restrict nuanced classification.     - Limited multi-labeling capabilities restrict nuanced classification.
     - Challenges in documenting clear and concise taxonomies.     - Challenges in documenting clear and concise taxonomies.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ==== Dr.Web ==== ==== Dr.Web ====
Line 64: Line 65:
     - Very low coverage.     - Very low coverage.
     - Lack of nuanced or detailed labeling reduces utility in research or marketing.     - Lack of nuanced or detailed labeling reduces utility in research or marketing.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ===== Marketing and Content Discovery ===== ===== Marketing and Content Discovery =====
Line 83: Line 84:
     - Precision and granularity can vary, sometimes complicating results.     - Precision and granularity can vary, sometimes complicating results.
     - Documentation and taxonomy definitions require improvement for research usability.     - Documentation and taxonomy definitions require improvement for research usability.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ===== General Classification with Human Contributions ===== ===== General Classification with Human Contributions =====
Line 94: Line 95:
     - Scalability issues due to reliance on human volunteers.     - Scalability issues due to reliance on human volunteers.
     - Low coverage and subjective biases in labeling.     - Low coverage and subjective biases in labeling.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ==== DMOZ (Curlie) ==== ==== DMOZ (Curlie) ====
Line 103: Line 104:
     - Extremely limited scalability due to a small number of editors.     - Extremely limited scalability due to a small number of editors.
     - Labels may be outdated due to infrequent updates for many categories.     - Labels may be outdated due to infrequent updates for many categories.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ===== Aggregated Services ===== ===== Aggregated Services =====
Line 114: Line 115:
     - Inconsistencies due to integration of outdated or non-standardized data.     - Inconsistencies due to integration of outdated or non-standardized data.
     - Lack of direct control over taxonomies used by aggregated providers.     - Lack of direct control over taxonomies used by aggregated providers.
-  TODO: URL, API+  <wrap todo>TODO: URL, API</wrap>
  
 ===== Company Datasets ===== ===== Company Datasets =====
 Compared to other services listed before, the following datasets are company-oriented instead of website-oriented. Some of them include website of the company, but this matching might be incomplete and might cause the following issues: Compared to other services listed before, the following datasets are company-oriented instead of website-oriented. Some of them include website of the company, but this matching might be incomplete and might cause the following issues:
-* If company owns multiple websites: + 
-** Likely only the main website will be listed. +  * If company owns multiple websites: 
-** This is especially pronounced with international versions of the website. +    * Likely only the main website will be listed. 
-* Likewise, the dataset may contain multiple companies for a given website: +    * This is especially pronounced with international versions of the website. 
-** Because of sister companies in a corporate. +  * Likewise, the dataset may contain multiple companies for a given website: 
-** Many small businesses list as their website social media. Sometimes, this link does not include the full path so a single-person company might indicate facebook.com as domain.+    * Because of sister companies in a corporate. 
 +    * Many small businesses list as their website social media. Sometimes, this link does not include the full path so a single-person company might indicate facebook.com as domain.
  
 ==== PeopleDataLabs ==== ==== PeopleDataLabs ====
Line 132: Line 134:
     - Based on LinkedIn profiles that are self-reported - prone to adversarial data.     - Based on LinkedIn profiles that are self-reported - prone to adversarial data.
     - Only a subset of PeopleDataLabs' full dataset (22M/70M rows, 10/78 columns).     - Only a subset of PeopleDataLabs' full dataset (22M/70M rows, 10/78 columns).
-  TODO: cite ''Machine Learning Compliance Analysis for Email Regulation'' when it is public.+  <wrap todo>TODO: cite ''Machine Learning Compliance Analysis for Email Regulation'' when it is public.</wrap>
  
 ==== Crunchbase ==== ==== Crunchbase ====
Line 143: Line 145:
     - URLs are extremely noisy (they are not the priority) (Source: Karel Kubicek's experience).     - URLs are extremely noisy (they are not the priority) (Source: Karel Kubicek's experience).
     - Focuses mostly on variables useful for investments and market competitiveness.     - Focuses mostly on variables useful for investments and market competitiveness.
-  TODO: cite ''Machine Learning Compliance Analysis for Email Regulation'' when it is public.+  <wrap todo>TODO: cite ''Machine Learning Compliance Analysis for Email Regulation'' when it is public.</wrap>
  
 ==== Orbis ==== ==== Orbis ====
Line 182: Line 184:
   * [[https://github.com/search?q=pihole%20blocklist&type=repositories]]: Search for pi-hole blocklists for specific uses.   * [[https://github.com/search?q=pihole%20blocklist&type=repositories]]: Search for pi-hole blocklists for specific uses.
   * [[https://oisd.nl/]], [[https://firebog.net/]]   * [[https://oisd.nl/]], [[https://firebog.net/]]
 +  * [[https://dsi.ut-capitole.fr/blacklists/index_en.php]] contains filtering designed for blocking university traffic. Contains many lists, from porn to malicious or misinformation content.
  
-Visit individual privacy-oriented pages for more details regarding classification of [[Privacy:Requests]], [[Privacy:Cookies]], and [[Privacy:Fingerprinting]].+Visit individual privacy-oriented pages for more details regarding classification of [[Privacy:Requests]], [[Privacy:Cookies]], [[Privacy:Fingerprinting]], and [[Privacy:JavaScript]].
  
 ==== Marketing Industry ==== ==== Marketing Industry ====
Line 233: Line 236:
 <bibtex bibliography></bibtex> <bibtex bibliography></bibtex>
  
-====== BibTex ====== 
-<bibtex database> 
-@inproceedings{vallina2020_misshapes, 
-    author = {Vallina, Pelayo and Le Pochat, Victor and Feal, \'{A}lvaro and Paraschiv, Marius and Gamba, Julien and Burke, Tim and Hohlfeld, Oliver and Tapiador, Juan and Vallina-Rodriguez, Narseo}, 
-    title = {Mis-shapes, Mistakes, Misfits: An Analysis of Domain Classification Services}, 
-    year = {2020}, 
-    isbn = {9781450381383}, 
-    publisher = {Association for Computing Machinery}, 
-    address = {New York, NY, USA}, 
-    url = {https://doi.org/10.1145/3419394.3423660}, 
-    doi = {10.1145/3419394.3423660}, 
-    abstract = {Domain classification services have applications in multiple areas, including cybersecurity, content blocking, and targeted advertising. Yet, these services are often a black box in terms of their methodology to classifying domains, which makes it difficult to assess their strengths, aptness for specific applications, and limitations. In this work, we perform a large-scale analysis of 13 popular domain classification services on more than 4.4M hostnames. Our study empirically explores their methodologies, scalability limitations, label constellations, and their suitability to academic research as well as other practical applications such as content filtering. We find that the coverage varies enormously across providers, ranging from over 90\% to below 1\%. All services deviate from their documented taxonomy, hampering sound usage for research. Further, labels are highly inconsistent across providers, who show little agreement over domains, making it difficult to compare or combine these services. We also show how the dynamics of crowd-sourced efforts may be obstructed by scalability and coverage aspects as well as subjective disagreements among human labelers. Finally, through case studies, we showcase that most services are not fit for detecting specialized content for research or content-blocking purposes. We conclude with actionable recommendations on their usage based on our empirical insights and experience. Particularly, we focus on how users should handle the significant disparities observed across services both in technical solutions and in research.}, 
-    booktitle = {Proceedings of the ACM Internet Measurement Conference}, 
-    pages = {598–618}, 
-    numpages = {21}, 
-    location = {Virtual Event, USA}, 
-    series = {IMC '20} 
-} 
-</bibtex> 
  
 +~~DISCUSSION~~
design/website_classification.1735839852.txt.gz · Last modified: by karelkubicek