---
title: Why is the domain name file bigger than the URL file?
description: Knowledge base article
---

[Skip to content](https://knowledge.whoisxmlapi.com/why-is-the-domain-file-bigger-than-the-url-file#main-content)

English

Show submenu for translations

![Logo inline notagline (1)-1.png\]](https://knowledge.whoisxmlapi.com/hs-fs/hubfs/Logo%20inline%20notagline%20(1)-1.png?height=40&name=Logo%20inline%20notagline%20(1)-1.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- Go to whoisxmlapi.com

 Go to whoisxmlapi.com

 What do you want to know?

- There are no suggestions because the search field is empty.

1. [Knowledge Base](https://knowledge.whoisxmlapi.com/?hsLang=en)
2. [Databases / Data Feeds](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en)
3. [Threat Intelligence Data Feeds (TIDF)](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#threat-intelligence-data-feeds-tidf)

# Why is the domain name file bigger than the URL file?

The files from Malicious domain name data feed and Malicious URL data feed contain different types of IoCs. Thus, their file sizes are not comparable.

If Malicious domain name data feed has a domain name, then all the URLs that belong to that domain name are probably also malicious.

However, if Malicious URL data feed has a URL, only that URL is malicious.

- [NRD2](https://knowledge.whoisxmlapi.com/nrd2?hsLang=en#main-content)

    - [Tutorials](https://knowledge.whoisxmlapi.com/nrd2?hsLang=en#tutorials)
- [General Support](https://knowledge.whoisxmlapi.com/general-support?hsLang=en)
- [WHOIS Domain Data](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#main-content)

    - [WHOIS vs. Historical WHOIS](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#whois-vs-historical-whois)
    - [Quarterly feeds](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#quarterly-feeds)
    - [WHOIS data fields](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#whois-data-fields)
    - [Bulk WHOIS Lookup](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#bulk-whois-lookup)
- [DNS Data](https://knowledge.whoisxmlapi.com/dns-data?hsLang=en)
- [APIs](https://knowledge.whoisxmlapi.com/apis?hsLang=en#main-content)

    - [WHOIS API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#whois-api)
    - [WHOIS History API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#whois-history-api)
    - [DNS Lookup API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#dns-lookup-api)
    - [IP Geolocation API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#ip-geolocation-api)
    - [Email Verification API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#email-verification-api)
    - [Domain Reputation API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#domain-reputation-api)
    - [Subdomain Lookup API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#subdomain-lookup-api)
    - [Reverse WHOIS API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#reverse-whois-api)
- [Databases / Data Feeds](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#main-content)

    - [Threat Intelligence Data Feeds (TIDF)](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#threat-intelligence-data-feeds-tidf)
    - [IP Geolocation / IP Netblocks Databases](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#ip-geolocation-ip-netblocks-databases)
- [Legacy](https://knowledge.whoisxmlapi.com/legacy?hsLang=en)
- [Dev & Data Science Corner](https://knowledge.whoisxmlapi.com/dev-data-science-corner?hsLang=en#main-content)

    - [Dev resources](https://knowledge.whoisxmlapi.com/dev-data-science-corner?hsLang=en#dev-resources)
- [Domain Research Suite (DRS)](https://knowledge.whoisxmlapi.com/domain-research-suite-drs-1?hsLang=en)
- [IP Data](https://knowledge.whoisxmlapi.com/ip-data?hsLang=en)

[![Chill listening crop-3](https://knowledge.whoisxmlapi.com/hs-fs/hubfs/Logo%20eye%20icon%20(1).png?width=37&height=24&name=Logo%20eye%20icon%20(1).png "Chill listening crop-3")](http://whoisxmlapi.com)

Copyright © 2026, whoisxmlapi.com