Fuzzy Domains API

Find domain names that look and sound exactly like your brand.

What is a Fuzzy Search? A fuzzy search searches for text that matches a term closely instead of exactly. This helps you find relevant results even when search terms are misspelled. A fuzzy search can get results when the correct spelling is not known as well as help find keywords that are loosely related to your search term. This is quite useful in finding other domain names that look and sound exactly like your brand name (domain's keyword). These domains might already be involved in Typosquatting and Phishing.

Find active domain names that look and sound exactly like your brand name through the following API:

https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com

Replace the key "XXXXX" with your own API key, generated through the Members Area.

Cost for Single Query = (3 API Credits for 100 Results)

{
    "success": true,
    "query": {
        "fuzzy_domains": "amazon.com",
        "page_size": 100
    },
    "count": {
        "total": 5237,
        "relation": "eq",
        "current": 100
    },
    "unique_domains": "hamazon.delivery, amaz0n.life, amazob.be, amason.net, amazin.beauty, 2mazon.buzz, amazan.xyz, amazomn.pl, amnazon.pl, emazon.in, amazonn.pl, amazyon.com, anmazon.me, ama-on.com, awazon.com, amazon1.mom, amazon6.top, amizon.info, 1amazon.info, kamazon.com.br, amazoon.makeup, eamazon.it, amazoo.net, amaazon.work, amazono.top, amazom.uno, amazpn.co, eamazon.asia, amazeon.xyz, amason.live, amauon.pl, aaazon.com, amayon.info, amazoin.us, amazone.ag, amason.top, amazone.parts, azmazon.work, amazan.top, amazoy.top, amzzon.co.uk, amazon2.shop, amazin.deals, ama-zon.pl, amazoq.com, xamazon.com, amzaon.cn, amazonn.today, qmazon.com.pl, amayon.ae, abazon.site, amagon.in, akmazon.com, amazaon.com.pl, emazon.pl, amaz6on.com, aamazon.ae, amqzon.uk, yamazon.info, am4azon.com, amaz2n.com, amazxon.work, amnazon.com.br, amazhn.com, amazom.online, amazo0n.work, anazon.top, amaozn.au, amwazon.work, zamazon.work, amozon.cm, acmazon.com, smazon.xyz, amaxon.com.pl, amazin.one, amazlon.net, amazcn.com, amaz9n.shop, amazons.video, amakon.biz, amazom.ltd, amqzon.co.nz, amazonk.club, amazom.space, amqzon.work, amazoo.xyz, amazeon.top, amazono.in, amazvn.com, amazon7.work, amazomn.co.uk, imazon.co, amazaon.xyz, samazon.biz, amaxon.shop, amaz0n.hair, amazoc.com, amazokn.com, amazonq.xyz, amazon2.top",
    "results": [
        {
            "num": 1,
            "domain_name": "hamazon.delivery",
            "domain_keyword": "hamazon",
            "domain_tld": "delivery",
            "query_time": "2023-05-22 09:50:20",
            "create_date": "2018-12-19",
            "update_date": "2023-02-02",
            "expiry_date": "2023-12-19",
            "registrar_iana": 48,
            "registrar_name": "eNom, LLC",
            "registrar_website": "http://www.enom.com",
            "registrant_name": "REDACTED FOR PRIVACY",
            "registrant_company": "Data Protected",
            "registrant_address": "REDACTED FOR PRIVACY",
            "registrant_city": "REDACTED FOR PRIVACY",
            "registrant_state": "WA",
            "registrant_zip": "REDACTED FOR PRIVACY",
            "registrant_country": "US",
            "registrant_email": "please query the rdds service of the registrar of record identified in this output for information on how to contact the registrant, admin, or tech contact of the queried domain name.",
            "registrant_phone": "REDACTED FOR PRIVACY",
            "registrant_fax": "REDACTED FOR PRIVACY",
            "name_servers": [
                "ns-1517.awsdns-61.org",
                "ns-1574.awsdns-04.co.uk",
                "ns-294.awsdns-36.com",
                "ns-826.awsdns-39.net"
            ],
            "domain_status": [
                "clientTransferProhibited"
            ],
            "dns_sec": [
                "unsigned"
            ]
        },
        {
            "num": 2,
            "domain_name": "amaz0n.life",
            "domain_keyword": "amaz0n",
            "domain_tld": "life",
            "query_time": "2023-05-30 03:23:15",
            "create_date": "2023-02-17",
            "update_date": "2023-02-22",
            "expiry_date": "2024-02-17",
            "registrar_iana": 1479,
            "registrar_name": "NameSilo, LLC",
            "registrar_website": "http://www.namesilo.com",
            "registrant_name": "REDACTED FOR PRIVACY",
            "registrant_company": "PrivacyGuardian.org llc",
            "registrant_address": "REDACTED FOR PRIVACY",
            "registrant_city": "REDACTED FOR PRIVACY",
            "registrant_state": "AZ",
            "registrant_zip": "REDACTED FOR PRIVACY",
            "registrant_country": "US",
            "registrant_email": "please query the rdds service of the registrar of record identified in this output for information on how to contact the registrant, admin, or tech contact of the queried domain name.",
            "registrant_phone": "REDACTED FOR PRIVACY",
            "registrant_fax": "REDACTED FOR PRIVACY",
            "name_servers": [
                "ns1.dnsowl.com",
                "ns2.dnsowl.com",
                "ns3.dnsowl.com"
            ],
            "domain_status": [
                "clientTransferProhibited"
            ],
            "dns_sec": [
                "unsigned"
            ]
        },
        {
            "num": 3,
            "domain_name": "amazob.be",
            "domain_keyword": "amazob",
            "domain_tld": "be",
            "query_time": "2023-05-30 03:27:50",
            "create_date": "2022-06-06",
            "registrar_name": "OVH",
            "registrar_website": "http://www.ovh.com",
            "name_servers": [
                "dns111.ovh.net",
                "ns111.ovh.net"
            ],
            "domain_status": [
                "Not Available",
                "clientTransferProhibited"
            ]
        },
        // remaining results truncated for easy viewing...
    ],
    "stats": {
        "total_time": 0.733,
        "api_credits_used": 3,
        "cost_calculation": "3 (fuzzy_domains [1 domain])"
    }
}

XML Format

By default, all results are sent in JSON format. To get results in XML format, simply add "&format=xml" to your query.

https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&format=xml

Cost for Single Query = (Same as with JSON Format)

Filter Results by Domain Extension

To only get results for a particular domain extension, simply add "&domain_tld=" to your query.

https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&domain_tld=com
https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&domain_tld=net
https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&domain_tld=co.uk

Cost for Single Query = (No extra API credits are charged to filter results by Domain Extension)

{
    "success": true,
    "query": {
        "fuzzy_domains": "amazon.com",
        "domain_tld": "co.uk",
        "page_size": 100
    },
    "count": {
        "total": 73,
        "relation": "eq",
        "current": 73
    },
    "unique_domains": "amzzon.co.uk, amazomn.co.uk, ramazon.co.uk, amagon.co.uk, amazojn.co.uk, amazom.co.uk, amazons.co.uk, afazon.co.uk, amazon2.co.uk, amazop.co.uk, amawzon.co.uk, samazon.co.uk, ammazon.co.uk, amayon.co.uk, ambazon.co.uk, amazkn.co.uk, amaxon.co.uk, asmazon.co.uk, wamazon.co.uk, avazon.co.uk, amadon.co.uk, emazon.co.uk, amazohn.co.uk, amajon.co.uk, amwzon.co.uk, amaon.co.uk, amazyn.co.uk, amazhon.co.uk, amazo.co.uk, amacon.co.uk, amzon.co.uk, mazon.co.uk, aazon.co.uk, amarin.co.uk, amazine.co.uk, amalone.co.uk, alanon.co.uk, abozon.co.uk, amarone.co.uk, abayon.co.uk, amazein.co.uk, amadox.co.uk, ama-zen.co.uk, amacor.co.uk, amaxpn.co.uk, amalor.co.uk, alizon.co.uk, amajons.co.uk, akadon.co.uk, aaaaon.co.uk, amanos.co.uk, amazgone.co.uk, amaxin.co.uk, amazeo.co.uk, alamon.co.uk, amaben.co.uk, amarzo.co.uk, a-mazin.co.uk, amasol.co.uk, amamazon.co.uk, agaton.co.uk, amasson.co.uk, aeagon.co.uk, aiamazon.co.uk, amanton.co.uk, amadan.co.uk, amaxos.co.uk, amaozan.co.uk, almazan.co.uk, amatou.co.uk, akazoo.co.uk, afmazone.co.uk, akazin.co.uk",
    "results": [
        {
            "num": 1,
            "domain_name": "amzzon.co.uk",
            "domain_keyword": "amzzon",
            "domain_tld": "co.uk",
            "query_time": "2023-07-20 01:37:35",
            "create_date": "2023-05-08",
            "update_date": "2023-05-08",
            "expiry_date": "2024-05-08",
            "registrar_name": "GoDaddy.com, LLC. [Tag = GODADDY]",
            "registrar_website": "http://uk.godaddy.com",
            "name_servers": [
                "ns49.domaincontrol.com",
                "ns50.domaincontrol.com"
            ],
            "domain_status": [
                "Registered until expiry date."
            ]
        },
        {
            "num": 2,
            "domain_name": "amazomn.co.uk",
            "domain_keyword": "amazomn",
            "domain_tld": "co.uk",
            "query_time": "2023-05-31 07:03:52",
            "create_date": "2004-04-26",
            "update_date": "2023-05-17",
            "expiry_date": "2024-04-26",
            "registrar_name": "Nom-IQ Limited t/a Com Laude [Tag = NOMIQ]",
            "registrar_website": "https://comlaude.com",
            "name_servers": [
                "ns1.amzndns.co.uk",
                "ns1.amzndns.com",
                "ns1.amzndns.net",
                "ns1.amzndns.org",
                "ns2.amzndns.co.uk",
                "ns2.amzndns.com",
                "ns2.amzndns.net",
                "ns2.amzndns.org"
            ],
            "domain_status": [
                "Registered until expiry date."
            ]
        },
        {
            "num": 3,
            "domain_name": "ramazon.co.uk",
            "domain_keyword": "ramazon",
            "domain_tld": "co.uk",
            "query_time": "2023-07-22 08:04:29",
            "create_date": "2022-08-25",
            "update_date": "2022-10-13",
            "expiry_date": "2023-08-25",
            "registrar_name": "John Thurlbeck t/a DOTSTERS [Tag = DOTSTERS]",
            "registrar_website": "http://dotsters.co.uk",
            "registrant_name": "John Thurlbeck",
            "name_servers": [
                "ns1.bodis.com",
                "ns2.bodis.com",
                "verification-103c5feb.ns3.dan.hosting"
            ],
            "domain_status": [
                "Registered until expiry date."
            ]
        },
        // remaining results truncated for easy viewing...
    ],
    "stats": {
        "total_time": 0.058,
        "api_credits_used": 3,
        "cost_calculation": "3 (fuzzy_domains [1 domain])"
    }
}

Count Total Results

The total count of results for your query will be provided in the following format:

"count": { "total": 5180, "relation": "eq", "current": 100 }

Generally the total results count can't be computed accurately without visiting all matches, which is costly for queries that match lots of documents. So, the API will count the total accurately up to 10,000 results. It is a good trade-off to speed up searches if you don't need the accurate number of results after a certain threshold. The "relation" determines how the "total" should be interpreted. A value of "gte" means that there might be more than the "total" results. When the relation has value of "eq", it indicates that "total" is the exact count. The value of "current" is the total number of results in current page.

Change Page Size

By default, 100 results are returned per query. To get more results, simply add "&page_size=" to your query.

https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&page_size=1000
https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&page_size=5000
https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&page_size=10000

Cost for Single Query = (Additional 1 API Credit for each 100 Results, Max 10000 Results Allowed)

Retrieve Only Domains

To get only domain names and skip the WHOIS data, simply add "&onlydomains" to your query.

https://api.bigdomaindata.com/?key=XXXXX&fuzzy_domains=amazon.com&onlydomains

Cost for Single Query = (Same as with WHOIS Data)

API Pricing and Packages

Can be used for Current WHOIS API, Bulk WHOIS API, WHOIS History API, Reverse WHOIS API and Fuzzy Domains API.

Package Quantity Price Rate Order
5,000 API Credits 5,000 $25 $5.00 Buy Now
25,000 API Credits 25,000 $100 $4.00 Buy Now
250,000 API Credits 250,000 $750 $3.00 Buy Now
1 Million API Credits Most Popular 1,000,000 $2,000 $2.00 Buy Now
10 Million API Credits 10,000,000 $10,000 $1.00 Buy Now

API Credits you purchase have lifetime validity, and you may use it whenever you wish. We accept Visa, Mastercard, American Express, Discover, Diners Club, JCB and China UnionPay. Popular payment wallets like Apple Pay, Google Pay, Alipay, WeChat Pay & Cash App Pay are accepted. You can also pay in installments through Buy Now, Pay Later (Affirm, Afterpay, Clearpay, Klarna) services. For orders worth $1000 and higher, you can also pay through Bank Wire Transfer (ACH, Fedwire and SWIFT). We also accept crypto payments through Bitcoin, Ethereum, Tether, Binance, Ripple and 100+ Cryptocurrencies.

Fuzzy Domains API

The Fuzzy Domains API is a technological tool developed to manage and procedure data in procedures where exactitude and even competition are not always feasible or expected. It influences the vision of "fuzzy matching," which is helpful in diverse requests, which include search engines, data cleaning, and natural language refining. Here is a complete summary of what the Fuzzy Domains API provides, its applications, and its fundamental devices.

What is Fuzzy Matching?

Fuzzy matching guides the method of discovering matches for data that are roughly equal but not exact. Far from even matching, which needs an accurate resemblance between the data features, fuzzy matching permits a degree of pliability. This can be particularly helpful when negotiating with misprints, typographical mistakes, or deviations in data structures.

Key Elements of the Fuzzy Domains API

  • Configurable Matching Rules: Users can tailor the matching rules as stated to their detailed needs. For example, they can modify the patience level for the discrepancy or describe detailed rules for managing standard mistakes in their data.
  • Error Tolerance: It is especially useful in climates where data entrances might have instability or errors. For example, in a database of company names, a search for "Microsoft" might yet return results for "Microsoft" or "Microsft," accepting standard typographical errors.
  • Similarity Scoring: The Fuzzy Domains API furnishes a resemblance score that evaluates how near two data access matches. This score can be used to rate results or choose the level of resemblance between search questions and database entrances.
  • Normalization: The API constantly contains elements for standardizing data to manage divergences in subsidizing, punctuation, and spacing. This assists in assuring that identical data access is remembered as matches despite little distinctions.
  • Flexible Search Capabilities: The Fuzzy Domains API is developed to improve search usefulness by permitting investigations that are indulgent of little differences or mistakes. This means that users can explore for terms that may be negligibly distinct from the planned question and yet acquire appropriate results.

Applications of the Fuzzy Domains API

  • Natural Language Processing (NLP): Fuzzy matching can be utilized in NLP tasks to enhance text resemblance efforts, commodity distinction, and opinion research, making the refining more vigorous to deviations in language use.
  • Search Engines: Improving search usefulness to account for typical misspellings, interpretations in search terms, and user information mistakes. This enhances the exactness and applicability of search results.
  • Data Cleaning: In data rehearsal tasks, specifically when combining datasets from diverse sources, unpredictability, and deviations in data access can be an issue. The API allows for normalizing and cleaning data by recognizing equivalent but not duplicate records.
  • Data Deduplication: In databases, particularly large ones, identical access can be a substantial issue. The Fuzzy Domains API can recognize and connect identical records that might not be accurate matches but convey the exact structure.
  • Customer Relationship Management (CRM): In CRM systems, the API can assist in fitting client documents that may have been documented dissimilarly in diverse systems or by different users, providing a suitable view of consumer details.

Challenges and References

  • User Knowledge: In search applications, furnishing users with feedback on the matching procedure (e.g., suggesting corrections or providing different queries) can improve the prevailing user knowledge.
  • Commission Influence: Fuzzy matching, especially on large data records, can be power-intensive. Maximizing methods and well-organized algorithms are necessary to preserve commission levels.
  • Exactness vs. Toleration: One of the foremost challenges in fuzzy matching is suspending accuracy with tolerance. High tolerance levels might enhance the probability of recovering appropriate results but can also lead to more false positives. Composing the API to match the detailed needs of the petition is required.
  • Customization: Different applications may require different matching criteria. The ability to customize and configure the fuzzy matching parameters is important to ensure that the API meets specific business needs.

Conclusion

The Fuzzy Domains API conveys a strong tool for managing data where actual matches are inoperable or disfavored. Combining fuzzy matching methods improves search abilities, enhances data standards, and authorizes more adaptable data refining. Whether used for data deduplication, search engine optimization, or natural language processing, the Fuzzy Domains API furnishes a robust explanation for organizing and examining imperfect data, making it an incalculable help in diverse technological and business situations.

FAQs Related To The Fuzzy Domains API

Q. How proper is the Fuzzy Domains API?

The precision of the Fuzzy Domains API relies on the composition and the algorithms used. While it furnishes flexible matching, the results might contain some false positives or negatives. Customizing the matching rules and modifying the patience levels can benefit proportion accuracy and recall.

Q. Can I merge the Fuzzy Domains API into my current systems?

Yes, the Fuzzy Domains API is created for easy integration. It generally provides RESTful endpoints or SDKs for diverse programming languages, permitting you to integrate them into your applications, databases, or systems seamlessly.

Q. What type of data can the Fuzzy Domains API procedure do?

The API can control diverse kinds of data which include text fields in databases, search queries, and customer records. It is sufficient for refining data with irregularity, such as names, addresses, and product definitions.

Fuzzy Domains Finder

Find domains that look and sound exactly like your domain through our free Fuzzy Domains Finder tool.

Powered by Current WHOIS Database

Our Current WHOIS Database contains the latest WHOIS of over 267 Million active domain names, that are currently registered. This powers our Fuzzy Domains API, which lets you quickly find all the domains that look and sound like your domain name.