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 <<>> 157.80.125.240
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42598
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;157.80.125.240.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 12:03:41 CST 2025
;; MSG SIZE  rcvd: 107
Host info
240.125.80.157.in-addr.arpa is an alias for 80.157.in-addr.arpa.
80.157.in-addr.arpa domain name pointer ibaraki.ac.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
240.125.80.157.in-addr.arpa	canonical name = 80.157.in-addr.arpa.
80.157.in-addr.arpa	name = ibaraki.ac.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
156.96.46.203 attackbots
Trying ports that it shouldn't be.
2019-12-19 03:02:37
122.228.19.80 attackspam
122.228.19.80 was recorded 105 times by 26 hosts attempting to connect to the following ports: 8087,5443,12345,1883,3388,4800,3260,623,9090,25,2048,8003,8123,4022,17185,21,1025,264,83,502,990,16993,2083,4070,520,5009,1010,993,2000,515,2087,771,4040,79,626,7547,636,9595,2123,40001,8069,9943,37777,2404,5006,8000,8060,3690,113,631,64738,3268,9306,5985,1962,9418,8554,8889,1777,1521,110,587,16992,8333,8010,5222,41794,5351,5984,7002,2480,3306,9000,28017,9600,4500,37215,789,3283,554,50070,9295,25565,1194,9191,5000,2525. Incident counter (4h, 24h, all-time): 105, 568, 20617
2019-12-19 03:25:54
188.162.199.222 attack
failed_logins
2019-12-19 03:14:31
188.166.246.46 attack
Dec 18 19:26:29 MK-Soft-VM5 sshd[19918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.246.46 
Dec 18 19:26:32 MK-Soft-VM5 sshd[19918]: Failed password for invalid user test from 188.166.246.46 port 43300 ssh2
...
2019-12-19 03:21:11
112.64.33.38 attackbotsspam
Invalid user !QAZ2wsx3edc from 112.64.33.38 port 43480
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.33.38
Failed password for invalid user !QAZ2wsx3edc from 112.64.33.38 port 43480 ssh2
Invalid user passwd01 from 112.64.33.38 port 34777
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.33.38
2019-12-19 02:52:54
79.137.116.6 attackspam
Dec 18 14:19:45 ny01 sshd[16304]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.116.6
Dec 18 14:19:47 ny01 sshd[16304]: Failed password for invalid user gutteridge from 79.137.116.6 port 53458 ssh2
Dec 18 14:24:46 ny01 sshd[16843]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.116.6
2019-12-19 03:29:43
129.204.83.118 attack
Dec 18 20:03:58 meumeu sshd[6618]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.83.118 
Dec 18 20:04:01 meumeu sshd[6618]: Failed password for invalid user renai from 129.204.83.118 port 42274 ssh2
Dec 18 20:10:18 meumeu sshd[7512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.83.118 
...
2019-12-19 03:12:09
184.105.139.114 attackbots
Dec 18 15:33:12 debian-2gb-nbg1-2 kernel: \[332365.945675\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=184.105.139.114 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=49548 DPT=9200 WINDOW=65535 RES=0x00 SYN URGP=0
2019-12-19 03:26:42
182.254.145.29 attack
Dec 18 16:33:59 MK-Soft-VM6 sshd[1546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.145.29 
Dec 18 16:34:01 MK-Soft-VM6 sshd[1546]: Failed password for invalid user kip from 182.254.145.29 port 55056 ssh2
...
2019-12-19 02:58:01
40.92.66.44 attackbots
Dec 18 17:33:46 debian-2gb-vpn-nbg1-1 kernel: [1057990.031838] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.66.44 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=61142 DF PROTO=TCP SPT=38190 DPT=25 WINDOW=0 RES=0x00 ACK RST URGP=0
2019-12-19 03:06:35
191.54.61.33 attackbots
Automatic report - Port Scan Attack
2019-12-19 03:09:40
42.61.59.36 attackbots
SSH authentication failure x 6 reported by Fail2Ban
...
2019-12-19 03:00:30
145.239.198.218 attack
Dec 18 19:00:57 herz-der-gamer sshd[972]: Invalid user zhangyulai987 from 145.239.198.218 port 44322
...
2019-12-19 03:16:07
119.84.70.193 attackbots
SSH invalid-user multiple login attempts
2019-12-19 03:21:37
217.182.79.118 attack
Dec 18 19:43:41 MainVPS sshd[366]: Invalid user aure from 217.182.79.118 port 59366
Dec 18 19:43:41 MainVPS sshd[366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.79.118
Dec 18 19:43:41 MainVPS sshd[366]: Invalid user aure from 217.182.79.118 port 59366
Dec 18 19:43:43 MainVPS sshd[366]: Failed password for invalid user aure from 217.182.79.118 port 59366 ssh2
Dec 18 19:48:58 MainVPS sshd[10354]: Invalid user foto1 from 217.182.79.118 port 38874
...
2019-12-19 02:51:09

Recently Reported IPs

75.138.149.77 121.47.71.216 248.98.153.186 233.198.90.192
226.208.238.105 205.94.146.210 167.172.243.181 236.210.117.94
206.108.142.26 29.235.186.101 205.3.12.69 14.104.207.88
179.183.86.220 228.93.138.244 194.50.157.59 245.2.16.38
41.23.99.79 89.162.108.205 113.84.150.237 176.89.48.232