https:\/\/www.aguse.jp\/<\/a> <\/figcaption><\/figure><\/div>\n\n\nUsing “aguse.jp” is simple. First, enter the URL you want to investigate on the homepage. The necessary information is the URL up to<\/p>\n\n\n\n
http:\/\/www.Monolith-law.jp<\/strong>\/article\/index.html<\/p>\n\n\n\nthe “www.Monolith-law.jp” part. This part is called the “hostname”.<\/p>\n\n\n\n
In the above example, everything after “\/article” is information about the location of that webpage within the server and is not necessary for identifying the server. On the other hand, the “www” part is a “subdomain”. Although you can set up any number of them within a single unique domain (Monolith-law.jp), if the subdomains are different, the web servers may also be different. In other words, if there are multiple subdomains like,<\/p>\n\n\n\n
https:\/\/monolith-law.jp
each subdomain may have a different web server. This is different from investigating the information of the domain registrant using “whois”.<\/p>\n\n\n\n
<\/span>How to Read the “aguse.jp” Investigation Results Page<\/span><\/h3>\n\n\n\nWhen you click “Search”, the investigation results page will be displayed.<\/p>\n\n\n
\n
The “Reverse Lookup Hostname” displays the “hostname” of the web server hosting the website in question.<\/p>\n\n\n
\n
And the information displayed under “Administrator Information for Forward Lookup IP Address \u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf” is about the administrator of the web server.<\/p>\n\n\n\n
<\/span>How to Investigate the Administrator<\/span><\/h3>\n\n\n\n
If you Google the string displayed here, you can identify the administrator of the web server. In this case, it was confirmed that “Sakura Internet Inc.” is managing “www.Monolith-law.jp”.<\/p>\n\n\n\n
<\/span>How does “aguse.jp” conduct its investigations?<\/span><\/h2>\n\n\n\nThe usage of “aguse.jp” as a web service is essentially exhausted in the above, but at this time, we will explain in more detail what kind of technical processing is being done, and why we can check the administrator information of the web server hosting the unique domain site in this way. After all, if you don’t understand “what you are doing”, you won’t be able to handle even a slightly exceptional case.<\/p>\n\n\n\n
<\/span>“IP Address” is an Address on the Internet<\/span><\/h3>\n\n\n\nFirstly, let’s start with what an “IP address” is. An IP address, also referred to as an “address on the internet,” is information that every machine connected to the internet (in principle) uniquely possesses. For instance, even when you browse this website on your smartphone, that smartphone has its own IP address.<\/p>\n\n\n\n
Similarly, just as the device browsing the website (such as a smartphone) has its own IP address, the website itself and the web server hosting that site also have their own IP addresses. Communication between machines on the internet, for example, “communication for browsing the Monolis Law Firm’s website on a smartphone,” always occurs between machines that have their own IP addresses.<\/p>\n\n\n\n
Between the smartphone with IP address \u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf and the web server with IP address \u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf, web page data and the like are exchanged.<\/p>\n\n\n\n
This is what it means to “browse a website using the internet.”<\/p>\n\n\n\n
<\/span>The Relationship Between “URL” and “Web Server’s IP Address”<\/span><\/h3>\n\n\n\nHowever, when users are surfing the internet, they are not consciously aware of the IP address of the website (or more accurately, the web server hosting it) they are viewing. This is because the communication based on IP addresses, as mentioned above, is primarily conducted within devices such as smartphones, and it is designed so that users do not need to be aware of the “IP address”. Instead, what users are conscious of is the URL.<\/p>\n\n\n\n
https:\/\/monolith.law\/article\/index.html<\/p>\n\n\n\n
Users surf the web while being aware of such URLs. When a user tries to open a URL like the one above, their device, such as a smartphone, performs the following processes:<\/p>\n\n\n\n
\nFirst, it investigates the IP address of the web server hosting the website of that URL<\/li>\n\n\n\n Then, it communicates with that IP address.<\/li>\n<\/ol>\n\n\n\n<\/span>What is “Forward Lookup” of a Hostname<\/span><\/h3>\n\n\n\nThe process mentioned above, specifically, converting the URL (more precisely, the “www.Monolith-law.jp” part of the URL, which is the “hostname”) into an IP address, is referred to as “forward lookup”.<\/p>\n\n\n
\n
When investigating a URL with “aguse.jp”, the information displayed in the “IP address (IP\u30a2\u30c9\u30ec\u30b9)” is the IP address that came out by “forward lookup” of the hostname part of the URL.<\/p>\n\n\n\n
<\/span>What is “Reverse Lookup” of an IP Address?<\/span><\/h3>\n\n\n\n“Reverse lookup” refers to the process of converting an IP address into a hostname, which is the opposite of “forward lookup”.<\/p>\n\n\n
\n
The “reverse lookup hostname (\u9006\u5f15\u304d\u30db\u30b9\u30c8\u540d)” of “aguse.jp” is displayed as follows:<\/p>\n\n\n\n
\nFirst, perform a forward lookup of the URL (specifically, the hostname part within the URL)<\/li>\n\n\n\n Then, perform a reverse lookup of the result to get the hostname<\/li>\n<\/ol>\n\n\n\nWhat complicates matters is that when you perform a “forward lookup \u2192 reverse lookup”, in the case of a custom domain site, the hostname of the rental server appears. This mechanism may seem a bit complicated, but we will explain it simply below.<\/p>\n\n\n\n
<\/span>What is a “Name Server”<\/span><\/h3>\n\n\n\nFirstly, “reverse lookup” is not necessarily a required process for internet use. As mentioned above, “forward lookup”, which is the process of finding the IP address of a web server based on a URL, is performed during regular internet browsing. However, “reverse lookup” does not typically appear in regular internet browsing or normal internet communication. The tool used to perform this “forward lookup” is what we call a “name server”.<\/p>\n\n\n\n
\nFirst, investigate the IP address of the URL (the web server hosting the website)<\/li>\n\n\n\n Communicate with the IP address<\/li>\n<\/ol>\n\n\n\nMore precisely, what is happening during this first step is:<\/p>\n\n\n\n
\nQuery the name server for the hostname of the URL (the web server hosting the website) you are trying to access<\/li>\n\n\n\n The name server responds with the IP address of the URL (the hostname of the web server hosting the website)<\/li>\n<\/ol>\n\n\n\nIn other words, a name server holds allocation information, such as “hostnames and their corresponding IP addresses”, much like a dictionary.<\/p>\n\n\n\n
<\/span>“Name Servers” and “Root Name Servers”<\/span><\/h3>\n\n\n\nName servers are countless on the internet. As mentioned above, a large number of inquiries are made during the process of surfing the internet. If there was a system where a single name server responded to all inquiries across the entire internet, the load on that server would be enormous. Therefore, there are countless name servers, and they are arranged on a tree, starting from a “root name server”, which is the master of the name servers. It’s like “Name servers (for example, A and B) hang under the root name server, and other name servers (for example, C and D) hang under name server A…” and so on.<\/p>\n\n\n\n
While it is desirable that all of these countless name servers on the internet always have the same dictionary information, trying to achieve this would also result in a huge workload. Therefore, in reality, perfect synchronization is not performed. It operates on a system where “there is information somewhere on the tree of name servers, and as long as there is information somewhere, you can get an answer eventually by asking in order.”<\/p>\n\n\n\n
<\/span>What is the “Reverse Lookup” of an IP Address?<\/span><\/h3>\n\n\n\nIn a “reverse lookup”, inquiries are made sequentially from the root name server to other name servers. This is the opposite of the usual inquiry (the inquiry during a forward lookup), asking for the hostname corresponding to the IP address \u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf.\u25cf\u25cf. The response to this inquiry is often a string related to the web server hosting the website. For example,<\/p>\n\n\n\n
\nWhen you perform a “forward lookup” on the hostname “Monolith-law.jp”, the returned IP address is “59.106.27.183”<\/li>\n\n\n\n When you perform a “reverse lookup” on the IP address “59.106.27.183”, the returned hostname is “www1943.sakura.ne.jp<\/strong>” (not “Monolith-law.jp”)<\/li>\n<\/ul>\n\n\n\nThen, the hostname “related to the web server hosting the website” includes the domain owned by the rental server operator in the case of a rental server, such as “sakura.ne.jp” in the above example.<\/p>\n\n\n\n
<\/span>Domain Whois Information of Rental Server Operators<\/span><\/h3>\n\n\n\nRental server operators often register accurate information on Whois.<\/p>\n\n\n
\n
Therefore, if you look up this domain name in ‘Whois’, you can obtain information about the rental server operator. For example, in the above case, you can find out that the ‘Operating Organization (\u904b\u55b6\u7d44\u7e54)’ is ‘SAKURA Internet Inc.’<\/p>\n\n\n\n
<\/span>Summary<\/span><\/h2>\n\n\n\nAs we have seen, investigating the hosting server provider that manages a site operating under a unique domain, in order to make deletion or IP address disclosure requests, is a complex matter in terms of IT. What we have explained in this article is merely the ‘basics’. When problems arise that cannot be overcome with basic knowledge alone, figuring out how to solve these problems becomes the ‘application’.<\/p>\n\n\n\n
Reputation management on the Internet is highly specialized, requiring expertise in both IT and law.<\/p>\n","protected":false},"excerpt":{"rendered":"
When making requests for deletion or disclosure of the poster’s IP address for articles on websites operated under so-called unique domains, the two possible parties to whom these requests can b […]<\/p>\n","protected":false},"author":32,"featured_media":67004,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[21,41],"acf":[],"_links":{"self":[{"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/posts\/59887"}],"collection":[{"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/comments?post=59887"}],"version-history":[{"count":4,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/posts\/59887\/revisions"}],"predecessor-version":[{"id":67005,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/posts\/59887\/revisions\/67005"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/media\/67004"}],"wp:attachment":[{"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/media?parent=59887"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/categories?post=59887"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monolith.law\/en\/wp-json\/wp\/v2\/tags?post=59887"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}