DNSWHOIS.INFO - 138.jp

Search for IP or hostnames:

138.jp checked at 2025-09-05T22:09:33.782Z 144ms 178/178/178 100% R:12

`138.jp`

NS	`anuj.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b41 ^{🇺🇸 Cloudflare}
			PTR	`anuj.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c141 ^{🇨🇷 Cloudflare}
			PTR	`anuj.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2141 ^{🇺🇸 Cloudflare}
			PTR	`anuj.ns.cloudflare.com`
		A	108.162.193.65^{🇺🇸 Cloudflare}
			PTR	`anuj.ns.cloudflare.com`
		A	172.64.33.65^{🇺🇸 Cloudflare}
			PTR	`anuj.ns.cloudflare.com`
		A	173.245.59.65^{🇺🇸 Cloudflare}
			PTR	`anuj.ns.cloudflare.com`
NS	`april.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a42 ^{🇺🇸 Cloudflare}
			PTR	`april.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c042 ^{🇨🇷 Cloudflare}
			PTR	`april.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2042 ^{🇺🇸 Cloudflare}
			PTR	`april.ns.cloudflare.com`
		A	108.162.192.66^{🇺🇸 Cloudflare}
			PTR	`april.ns.cloudflare.com`
		A	172.64.32.66^{🇺🇸 Cloudflare}
			PTR	`april.ns.cloudflare.com`
		A	173.245.58.66^{🇺🇸 Cloudflare}
			PTR	`april.ns.cloudflare.com`
MX	`amir.mx.cloudflare.net`
		A	2606:4700:f5::11 ^{🇺🇸 Cloudflare}
		A	2606:4700:f5::12 ^{🇺🇸 Cloudflare}
		A	2606:4700:f5::13 ^{🇺🇸 Cloudflare}
		A	162.159.205.11^Cloudflare
		A	162.159.205.12^Cloudflare
		A	162.159.205.13^Cloudflare
MX	`isaac.mx.cloudflare.net`
		A	2606:4700:f5::e ^{🇺🇸 Cloudflare}
		A	2606:4700:f5::f ^{🇺🇸 Cloudflare}
		A	2606:4700:f5::10 ^{🇺🇸 Cloudflare}
		A	162.159.205.17^Cloudflare
		A	162.159.205.18^Cloudflare
		A	162.159.205.19^Cloudflare
MX	`linda.mx.cloudflare.net`
		A	2606:4700:f5::b ^{🇺🇸 Cloudflare}
		A	2606:4700:f5::c ^{🇺🇸 Cloudflare}
		A	2606:4700:f5::d ^{🇺🇸 Cloudflare}
		A	162.159.205.23^Cloudflare
		A	162.159.205.24^Cloudflare
		A	162.159.205.25^Cloudflare
A	107.172.217.118^{🇺🇸 ColoCrossing}
		PTR	`107-172-217-118-host.colocrossing.com`

`jp`

	NS	`a.dns.jp`
	NS	`b.dns.jp`
	NS	`c.dns.jp`
	NS	`d.dns.jp`
	NS	`e.dns.jp`
	NS	`f.dns.jp`
	NS	`g.dns.jp`
	NS	`h.dns.jp`

Starts with same word
`138.io`
`138.biz`
`138.bet`
`138.in-addr.arpa`
`138.ru`
`138.games`
`138.world`
`138.city`
`138.be`
`138.com`
`138.net`
`138.media`
`138.us`
`138.cash`
`138.it`
`138.mg`
`138.la`
`138.co`
`138.cc`
`138.lv`
`138.chat`
`138.org`
`138.casino`
`138.one`
`138.network`
`138.ph`
`138.ac`
`138.hu`
`138.by`
`138.cn`
`138.im`
`138.info`
`138.at`
`138.pl`
`138.co.jp`
`138.nl`
`138.fr`
`138.gd`
`138.tel`
`138.tv`
`138.am`
`138.me`
`138.lu`
`138.jp`
`138.eu`
`138.cm`

Starts similarily
`183.co`
`138.hu`
`813.com.tw`
`381.ph`
`138.by`
`183.fr`
`138.cn`
`138.im`
`183.tw`
`138.info`
`138.at`
`318.jp`
`381.ir`
`138.pl`
`318.studio`
`138.co.jp`
`381.us`
`138.nl`
`318.ir`
`138.fr`
`381.me`
`813.org`
`183.com.cn`
`813.ru`
`813.fm`
`831.net`
`138.gd`
`381.in`
`831.pl`
`183.ca`
`138.tel`
`138.tv`
`831.es`
`318.cool`
`318.cn`
`138.am`
`381.ca`
`318.biz`
`318.cc`
`183.com`
`381.biz`
`183.ru`
`318.org`
`381.de`
`138.me`
`138.lu`
`318.org.uk`
`183.app`
`318.ru`
`138.jp`
`318.fr`
`318.coffee`
`138.eu`
`813.ch`
`138.cm`
`813.de`
`318.in`
`381.cn`
`138.io`
`183.eu`
`183.de`
`381.dk`
`138.biz`
`831.cc`
`138.bet`
`318.net`
`318.dk`
`381.com.tw`
`183.nl`
`138.in-addr.arpa`
`813.fr`
`813.nl`
`138.ru`
`831.tv`
`381.pl`
`831.ru`
`183.in`
`138.games`
`138.world`
`183.ph`
`813.hk`
`138.city`
`138.be`
`183.vip`
`138.com`
`813.pl`
`318.com`
`318.ag`
`381.net`
`183.pw`
`183.us`
`183.com.au`
`813.jp`
`318.nu`
`138.net`
`381.fr`
`138.media`
`318.ca`
`318.co.kr`
`831.de`

AI analysis

The IP number 107.172.217.118 is pointed to by 138.jp.

IP numbers are shared between 138.jp and other host names such as teddysum.com, weibo.jp, sunyanxi.com, ovz.jp, and gov.com.se.

Two name servers, anuj.ns.cloudflare.com and april.ns.cloudflare.com, are delegated to 138.jp.

The name server setup of 138.jp is identical to that of other domains such as screenmanager.cz, weibo.jp, lamp.sh, sunyanxi.com, and preseliventure.co.uk.

For instance, the name servers of 138.jp at least partially share with other domains such as aracajufest.com.br, q-itservices.com, survivalbrasil.org, greenforest.gr, and qtizy.cn.

The name servers sharon.ns.cloudflare.com are frequently utilized in conjunction.

anuj.ns.cloudflare.com and april.ns.cloudflare.com each point to six IP numbers: 2606:4700:58::adf5:3b41, 2803:f800:50::6ca2:c141, 2a06:98c1:50::ac40:2141, 108.162.193.65, 172.64.33.65, and 173.245.59.65 for anuj.ns.cloudflare.com, and 2606:4700:50::adf5:3a42, 2803:f800:50::6ca2:c042, 2a06:98c1:50::ac40:2042, 108.162.192.66, 172.64.32.66, and 173.245.58.66 for april.ns.cloudflare.com.

Three mail servers, amir.mx.cloudflare.net, isaac.mx.cloudflare.net, and linda.mx.cloudflare.net, are responsible for handling 138.jp.

Some mail servers are partially shared by 138.jp with other domains such as gamistan.com, kat.pw, geniuszone.biz, omegax.net, and bgit.net.

amir.mx.cloudflare.net, isaac.mx.cloudflare.net, and linda.mx.cloudflare.net point to six IP numbers each: 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.11, 162.159.205.12, 162.159.205.13 for amir.mx.cloudflare.net; 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18, 162.159.205.19 for isaac.mx.cloudflare.net; and 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.23, 162.159.205.24, 162.159.205.25 for linda.mx.cloudflare.net.

dbq