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: Germany

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

;; QUESTION SECTION:
;134.119.233.12.			IN	A

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

;; Query time: 99 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:39:46 CST 2022
;; MSG SIZE  rcvd: 107
Host info
12.233.119.134.in-addr.arpa domain name pointer m12s6-5-1db.ispgateway.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.233.119.134.in-addr.arpa	name = m12s6-5-1db.ispgateway.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
14.236.122.103 attackbots
Unauthorized connection attempt detected from IP address 14.236.122.103 to port 445
2019-12-24 04:06:28
103.238.213.158 attack
3389/tcp 3389/tcp 3389/tcp
[2019-12-18/22]3pkt
2019-12-24 04:06:11
123.7.118.185 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 04:09:56
116.211.118.249 attack
23/tcp 23/tcp 23/tcp...
[2019-10-22/12-23]44pkt,1pt.(tcp)
2019-12-24 04:38:22
123.30.179.215 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 04:25:42
195.206.60.141 attackbotsspam
23/tcp 23/tcp 23/tcp...
[2019-11-12/12-22]11pkt,1pt.(tcp)
2019-12-24 04:16:23
81.22.45.83 attackbotsspam
3389/tcp 3389/tcp 3389/tcp...
[2019-10-25/12-22]98pkt,1pt.(tcp)
2019-12-24 04:21:22
182.160.102.110 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 04:17:47
58.210.6.51 attack
Dec 23 16:44:21 eventyay sshd[4154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.210.6.51
Dec 23 16:44:23 eventyay sshd[4154]: Failed password for invalid user mysql from 58.210.6.51 port 24556 ssh2
Dec 23 16:51:28 eventyay sshd[4376]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.210.6.51
...
2019-12-24 04:13:29
124.158.160.34 attackbotsspam
445/tcp 445/tcp 445/tcp...
[2019-10-26/12-22]29pkt,1pt.(tcp)
2019-12-24 04:19:14
222.73.85.7 attackbotsspam
1433/tcp 445/tcp...
[2019-11-27/12-22]11pkt,2pt.(tcp)
2019-12-24 04:40:31
129.204.194.146 attackspambots
Oct 31 15:08:59 yesfletchmain sshd\[6430\]: Invalid user suherman from 129.204.194.146 port 59374
Oct 31 15:09:00 yesfletchmain sshd\[6430\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.194.146
Oct 31 15:09:01 yesfletchmain sshd\[6430\]: Failed password for invalid user suherman from 129.204.194.146 port 59374 ssh2
Oct 31 15:15:01 yesfletchmain sshd\[6816\]: Invalid user attack from 129.204.194.146 port 41816
Oct 31 15:15:01 yesfletchmain sshd\[6816\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.194.146
...
2019-12-24 04:23:18
121.182.166.82 attackbotsspam
Dec 23 15:43:56 hcbbdb sshd\[32392\]: Invalid user zoltrix from 121.182.166.82
Dec 23 15:43:56 hcbbdb sshd\[32392\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.182.166.82
Dec 23 15:43:58 hcbbdb sshd\[32392\]: Failed password for invalid user zoltrix from 121.182.166.82 port 22211 ssh2
Dec 23 15:50:04 hcbbdb sshd\[654\]: Invalid user hgfdsa from 121.182.166.82
Dec 23 15:50:04 hcbbdb sshd\[654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.182.166.82
2019-12-24 04:12:58
129.204.202.89 attackbotsspam
Dec 15 11:27:29 yesfletchmain sshd\[19328\]: User root from 129.204.202.89 not allowed because not listed in AllowUsers
Dec 15 11:27:29 yesfletchmain sshd\[19328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.202.89  user=root
Dec 15 11:27:30 yesfletchmain sshd\[19328\]: Failed password for invalid user root from 129.204.202.89 port 57803 ssh2
Dec 15 11:34:02 yesfletchmain sshd\[19677\]: Invalid user marin from 129.204.202.89 port 33469
Dec 15 11:34:02 yesfletchmain sshd\[19677\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.202.89
...
2019-12-24 04:04:10
129.204.120.42 attackbots
Feb 14 16:36:20 dillonfme sshd\[10403\]: Invalid user eli from 129.204.120.42 port 44090
Feb 14 16:36:20 dillonfme sshd\[10403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.120.42
Feb 14 16:36:22 dillonfme sshd\[10403\]: Failed password for invalid user eli from 129.204.120.42 port 44090 ssh2
Feb 14 16:43:40 dillonfme sshd\[10910\]: Invalid user tf2 from 129.204.120.42 port 35240
Feb 14 16:43:40 dillonfme sshd\[10910\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.120.42
...
2019-12-24 04:41:59

Recently Reported IPs

134.119.225.129 134.119.225.41 134.119.225.194 134.119.225.23
134.119.233.19 134.119.233.95 134.119.234.155 134.119.233.46
134.119.234.28 134.119.234.198 134.119.234.170 134.119.234.32
134.119.234.183 134.119.234.54 134.119.240.24 134.119.244.172
134.119.244.188 134.119.246.227 134.119.241.191 134.119.247.10