Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Japan

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 202.122.248.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19756
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;202.122.248.52.			IN	A

;; AUTHORITY SECTION:
.			29	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025020500 1800 900 604800 86400

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 15:25:03 CST 2025
;; MSG SIZE  rcvd: 107
Host info
52.248.122.202.in-addr.arpa domain name pointer 202-122-248-52.cidr10.kct.ad.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.248.122.202.in-addr.arpa	name = 202-122-248-52.cidr10.kct.ad.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.88.112.115 attackbots
Mar  9 03:57:00 firewall sshd[14888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.115  user=root
Mar  9 03:57:02 firewall sshd[14888]: Failed password for root from 49.88.112.115 port 26585 ssh2
Mar  9 03:57:05 firewall sshd[14888]: Failed password for root from 49.88.112.115 port 26585 ssh2
...
2020-03-09 15:57:50
134.175.42.252 attackbots
DATE:2020-03-09 04:49:08, IP:134.175.42.252, PORT:ssh SSH brute force auth (docker-dc)
2020-03-09 16:03:45
36.79.18.90 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-09 16:18:51
125.25.245.236 attack
1583725759 - 03/09/2020 04:49:19 Host: 125.25.245.236/125.25.245.236 Port: 445 TCP Blocked
2020-03-09 15:58:16
122.227.230.11 attackspam
fail2ban -- 122.227.230.11
...
2020-03-09 16:09:50
220.120.106.254 attackbotsspam
2020-03-09T04:01:28.201540shield sshd\[22394\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.120.106.254  user=root
2020-03-09T04:01:30.094900shield sshd\[22394\]: Failed password for root from 220.120.106.254 port 57552 ssh2
2020-03-09T04:03:56.303405shield sshd\[22869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.120.106.254  user=root
2020-03-09T04:03:58.181793shield sshd\[22869\]: Failed password for root from 220.120.106.254 port 52472 ssh2
2020-03-09T04:06:28.834227shield sshd\[23335\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.120.106.254  user=root
2020-03-09 15:56:36
177.126.129.6 attackspambots
" "
2020-03-09 16:11:31
222.186.180.223 attackspam
Mar  9 09:23:10 srv206 sshd[28713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
Mar  9 09:23:11 srv206 sshd[28713]: Failed password for root from 222.186.180.223 port 28728 ssh2
...
2020-03-09 16:26:07
119.42.123.181 attackbotsspam
Automatic report - Port Scan Attack
2020-03-09 16:08:55
159.65.145.106 attack
Automatic report - XMLRPC Attack
2020-03-09 16:16:51
192.184.46.241 attackspambots
20/3/8@23:49:25: FAIL: Alarm-Intrusion address from=192.184.46.241
...
2020-03-09 15:54:40
180.76.148.147 attackspambots
3x Failed Password
2020-03-09 16:09:33
210.71.232.236 attackspam
Mar  9 06:09:04 vserver sshd\[6612\]: Invalid user mailman from 210.71.232.236Mar  9 06:09:07 vserver sshd\[6612\]: Failed password for invalid user mailman from 210.71.232.236 port 37228 ssh2Mar  9 06:13:12 vserver sshd\[6646\]: Invalid user ubuntu from 210.71.232.236Mar  9 06:13:14 vserver sshd\[6646\]: Failed password for invalid user ubuntu from 210.71.232.236 port 45794 ssh2
...
2020-03-09 16:16:26
143.215.247.68 attack
143.215.247.68 was recorded 469 times by 6 hosts attempting to connect to the following ports: 593,3283,9876,161,192,69,111,162,520,1025,4136,1900,9535,1434,17708,1646,1027,7,3456,27599,58800,64588,48478,1026,1433,445,26617,57473,2048,54024,2049,518,50986,514,1645,5060,999,20031,62185,38392,998,626,18602,54553,33577,46656,123,2222,37375,4500,6000,34257,7966,42096,37376,23920,65356,15048,23350,500,49152,62019,48943,50528,51263,631,53650,49153,136,10497,27071,3127,54120,15158,20168,135,10002,44227,49154,1701,997,62373,61198,16518,31632,139,5353,64729,996,63805,1812,53,25486,56403,49524,43063,51006,57523,44689,44518,32768,19552,25163,18282,21245. Incident counter (4h, 24h, all-time): 469, 2907, 3966
2020-03-09 16:05:15
121.204.150.38 attackspam
Mar  9 07:26:18 takio sshd[3614]: Invalid user novogrow123 from 121.204.150.38 port 37516
Mar  9 07:39:43 takio sshd[3772]: Invalid user www from 121.204.150.38 port 33104
Mar  9 07:47:24 takio sshd[3827]: Invalid user novogrow from 121.204.150.38 port 59134
2020-03-09 15:58:32

Recently Reported IPs

65.105.45.216 211.82.79.19 252.3.223.148 49.160.230.161
173.245.34.82 199.221.137.17 221.251.71.171 228.231.210.200
74.32.53.18 58.218.28.15 172.217.192.128 143.220.104.112
56.1.93.125 177.40.59.102 176.36.100.208 161.17.226.199
64.126.88.67 64.153.150.111 248.201.152.46 230.98.224.179