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

;; QUESTION SECTION:
;133.107.80.18.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 02:20:00 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 18.80.107.133.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 18.80.107.133.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
132.248.88.77 attackbotsspam
Repeated brute force against a port
2020-01-14 07:56:40
151.80.19.228 attack
Jan 13 23:02:50 email sshd\[19624\]: Invalid user anaum from 151.80.19.228
Jan 13 23:02:50 email sshd\[19624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.19.228
Jan 13 23:02:52 email sshd\[19624\]: Failed password for invalid user anaum from 151.80.19.228 port 38322 ssh2
Jan 13 23:02:58 email sshd\[19652\]: Invalid user hromecb from 151.80.19.228
Jan 13 23:02:58 email sshd\[19652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.19.228
...
2020-01-14 08:27:31
93.174.93.123 attackbots
Jan 14 01:01:08 debian-2gb-nbg1-2 kernel: \[1219370.490498\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=93.174.93.123 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=41177 PROTO=TCP SPT=52217 DPT=2140 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-14 08:08:32
103.31.249.48 attackspam
Wordpress Admin Login attack
2020-01-14 08:15:02
36.228.104.238 attackspambots
Jan 13 22:20:54 debian-2gb-nbg1-2 kernel: \[1209756.251452\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=36.228.104.238 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=48878 PROTO=TCP SPT=39324 DPT=23 WINDOW=29033 RES=0x00 SYN URGP=0
2020-01-14 08:20:16
210.245.87.199 attackbotsspam
Jan 13 22:20:19 mxgate1 postfix/postscreen[2524]: CONNECT from [210.245.87.199]:52739 to [176.31.12.44]:25
Jan 13 22:20:19 mxgate1 postfix/dnsblog[2667]: addr 210.245.87.199 listed by domain zen.spamhaus.org as 127.0.0.2
Jan 13 22:20:19 mxgate1 postfix/dnsblog[2666]: addr 210.245.87.199 listed by domain b.barracudacentral.org as 127.0.0.2
Jan 13 22:20:25 mxgate1 postfix/postscreen[2524]: DNSBL rank 3 for [210.245.87.199]:52739
Jan x@x
Jan 13 22:20:26 mxgate1 postfix/postscreen[2524]: DISCONNECT [210.245.87.199]:52739


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=210.245.87.199
2020-01-14 07:59:03
218.92.0.184 attack
20/1/13@18:51:12: FAIL: IoT-SSH address from=218.92.0.184
...
2020-01-14 07:53:05
218.65.35.26 attackspambots
" "
2020-01-14 08:13:06
205.209.158.46 attack
20/1/13@16:21:52: FAIL: Alarm-Network address from=205.209.158.46
20/1/13@16:21:52: FAIL: Alarm-Network address from=205.209.158.46
20/1/13@16:21:52: FAIL: Alarm-Network address from=205.209.158.46
...
2020-01-14 07:53:40
51.79.32.154 attackspam
Honeypot hit: [2020-01-14 00:21:46 +0300] Connected from 51.79.32.154 to (HoneypotIP):110
2020-01-14 07:57:32
213.14.161.71 attack
Unauthorized connection attempt detected from IP address 213.14.161.71 to port 23 [J]
2020-01-14 08:19:00
200.89.159.83 attackbotsspam
scan r
2020-01-14 08:26:43
185.214.164.10 attackspam
2 attempts against mh-modsecurity-ban on web2.any-lamp.com
2020-01-14 08:14:34
81.67.105.140 attackbotsspam
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:19:32 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:19:47 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:20:03 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:20:19 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:20:35 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:20:51 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:21:07 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:21:23 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:21:39 +0100] "POST /[munged]: HTTP/1.1" 200 6578 "-" "-"
[munged]::443 81.67.105.140 - - [13/Jan/2020:22:21:55 +0100] "POST /[munged]: H
2020-01-14 07:50:13
190.219.237.92 attackspam
firewall-block, port(s): 5555/tcp
2020-01-14 08:16:20

Recently Reported IPs

154.29.136.133 195.83.145.126 119.28.179.192 238.74.252.23
21.73.74.52 103.132.163.49 249.219.37.8 45.149.188.161
19.171.49.190 118.217.152.13 231.202.237.224 47.184.91.94
4.150.54.158 231.100.140.224 60.215.235.187 215.33.49.18
249.245.99.200 230.238.140.216 66.10.65.226 129.113.207.80