Naver Yeti Spider API

Latest Naver Yeti Spider user agents detected

Naver Yeti Spider API documentation

The Naver Yeti Spider API makes it easy to check if an IP address is officially used by Naver Yeti Spider to crawl the web, including your website.

The Naver Yeti Spider API is a 'REST API' which is accessible via HTTPS using the GET method at a predefined URL. It returns either JSON of plain text response.

Benefits of using the Naver Yeti Spider API are:

• Querying the Naver Yeti Spider API is free of charge and anonymous.
• The Naver Yeti Spider API works across applications and scripting languages, e.g. see below the Google Spreadsheets and Python implementations.
• The Naver Yeti Spider API contains historical records, which means that IP addresses which may have been once used but are currently not resolving can still be identified when performing log file analysis on historical logs.
• As Naver Yeti Spider is crawling the web, the database for the Naver Yeti Spider API is continuously and automatically updated with the latest IP addresses and user agents.
• Instead of performing two seperate lookups (forward and reverse) with the 'host' command on the command line locally, this API provides a single lookup method which can be accessed from anywhere.
• The Naver Yeti Spider API contains one of the largest freely and publicly accessible collection of IP addresses for Naver Yeti Spider.

This Naver Yeti Spider API is coded and provided by ex-Google engineer and technical SEO expert Fili.

Authentication

This Naver Yeti Spider API is free of charge and can be accessed without credentials. If you have any questions about using the Naver Yeti Spider API on a larger scale or like to discuss ways to utilize this database internally, contact Fili.

Quickstart guide

You can query the API endpoint using a GET request and replace IPADDRESS with the IP address you wish to query.

        https://naverbot.seoapi.com/v1/validate/?ip=IPADDRESS
    

Endpoint definitions

By default the API will return a JSON response with:

• a body containing "valid": "true" if the queried IP address is found in the database,
• or a body containing "valid": "false" if the queried IP address is not found in the database.

Alternatively, it is also possible to request just a BOOLEAN in plain text (useful in some situations, e.g. Google Spreadsheets - see below).

URL parameters which are accepted by the Naver Yeti Spider API are:

Code snippets

Here are some examples of how to query the Naver Yeti Spider API:

Command line (curl) Example 1

        curl -i https://naverbot.seoapi.com/v1/validate/?ip=110.93.150.102
    

It is also possible to use this API in Google Spreadsheets by adding &compact=1 to the API URL.

In the following example, the content of cell A1 contains the IP address to check and replaces in the =IMPORTDATA formula the __IPADDRESS__. Be sure to replace the cell ID when using this in Google Spreadsheets.

Google Spreadsheets

        =IMPORTDATA(SUBSTITUTE("https://naverbot.seoapi.com/v1/validate/?ip=__IPADDRESS__&compact=1","__IPADDRESS__",A1))
    

It is also possible to use this API in your code with python or similar other languages.

Python 3

        import requests

r = requests.get(
    'https://naverbot.seoapi.com/v1/validate/?ip=110.93.150.102'
).json()
print(r.get('valid', None))
    

Example responses

When the URL parameter compact is missing or has a value of 0 (zero) the API returns a JSON response with a queried IP address, query timestamp and boolean if the IP address validates.

Example 1: JSON response

        {
    "ip": "110.93.150.102",
    "timestamp": 1615471876.25665,
    "valid": true
}
    

Example 2: JSON response

        {
    "ip": "127.0.0.1",
    "timestamp": 1615471876.25665,
    "valid": false
}
    

When the URL parameter compact is present and has a value of 1 (one) the API returns a plain text response with a boolean if the IP address validates.

Example 3: plain text (compact) response

        true
    

Example 4: plain text (compact) response

        false
    

Latest IP addresses added

• 110.93.150.102
• 114.111.32.135
• 110.93.150.89
• 211.249.46.212
• 114.111.32.50
• 110.93.150.200
• 110.93.150.174
• 110.93.150.109
• 114.111.32.217
• 211.249.46.122
• 114.111.32.116
• 110.93.150.181
• 211.249.46.200
• 114.111.32.96
• 211.249.46.124
• 110.93.150.156
• 211.249.46.163
• 114.111.32.30
• 110.93.150.190
• 114.111.32.24
• 211.249.46.90
• 211.249.46.191
• 114.111.32.159
• 110.93.150.217

Disclaimer

The data shown on this website is automatically collected from multiple sources, mostly websites and domains under the control of ex-Google engineer Fili. The SEO APIs on this website are under constant development and improvements will be added over time.

Any data and/or query submitted to this website or its APIs are only used to verify whether an IP address is associated with a known search bot. When not, the IP address (or any other submitted data) is completely disregarded and ignored. Only after an IP address is separately confirmed to be a search bot IP address, the IP address is anonymously stored for future queries.

Bugs will happen. Despite best efforts to maintain the code base and data quality, no guarantees can or will be given. Data may be incomplete and/or errors may occur. This is a personal website and for-fun project. Use at your own risk.