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

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

;; QUESTION SECTION:
;134.119.0.100.			IN	A

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

;; Query time: 149 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:01:42 CST 2022
;; MSG SIZE  rcvd: 106
Host info
100.0.119.134.in-addr.arpa domain name pointer ms10684.ispgateway.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
100.0.119.134.in-addr.arpa	name = ms10684.ispgateway.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
122.146.12.19 attack
Jan 25 05:47:16 ns392434 sshd[15083]: Invalid user guo from 122.146.12.19 port 40666
Jan 25 05:47:16 ns392434 sshd[15083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.146.12.19
Jan 25 05:47:16 ns392434 sshd[15083]: Invalid user guo from 122.146.12.19 port 40666
Jan 25 05:47:18 ns392434 sshd[15083]: Failed password for invalid user guo from 122.146.12.19 port 40666 ssh2
Jan 25 05:50:01 ns392434 sshd[15103]: Invalid user dm from 122.146.12.19 port 37802
Jan 25 05:50:01 ns392434 sshd[15103]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.146.12.19
Jan 25 05:50:01 ns392434 sshd[15103]: Invalid user dm from 122.146.12.19 port 37802
Jan 25 05:50:03 ns392434 sshd[15103]: Failed password for invalid user dm from 122.146.12.19 port 37802 ssh2
Jan 25 05:52:36 ns392434 sshd[15176]: Invalid user nagios from 122.146.12.19 port 33428
2020-01-25 16:05:33
92.118.160.33 attack
Unauthorized connection attempt detected from IP address 92.118.160.33 to port 8531 [T]
2020-01-25 16:42:03
123.206.68.35 attackspam
Jan 25 14:34:00 webhost01 sshd[25866]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.68.35
Jan 25 14:34:02 webhost01 sshd[25866]: Failed password for invalid user ana from 123.206.68.35 port 46670 ssh2
...
2020-01-25 16:19:17
218.92.0.173 attackbots
Jan 25 08:32:14 hcbbdb sshd\[30647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.173  user=root
Jan 25 08:32:15 hcbbdb sshd\[30647\]: Failed password for root from 218.92.0.173 port 38923 ssh2
Jan 25 08:32:19 hcbbdb sshd\[30647\]: Failed password for root from 218.92.0.173 port 38923 ssh2
Jan 25 08:32:22 hcbbdb sshd\[30647\]: Failed password for root from 218.92.0.173 port 38923 ssh2
Jan 25 08:32:25 hcbbdb sshd\[30647\]: Failed password for root from 218.92.0.173 port 38923 ssh2
2020-01-25 16:40:59
185.142.236.35 attackspam
01/25/2020-03:25:46.741615 185.142.236.35 Protocol: 6 ET SCAN Suspicious inbound to Oracle SQL port 1521
2020-01-25 16:40:12
185.232.67.6 attackbots
Jan 25 09:02:14 dedicated sshd[10508]: Invalid user admin from 185.232.67.6 port 58365
2020-01-25 16:17:34
54.37.205.162 attackspambots
Invalid user sybase from 54.37.205.162 port 44964
2020-01-25 16:20:26
122.51.240.250 attackbots
Automatic report - SSH Brute-Force Attack
2020-01-25 16:40:38
154.211.6.65 attackbotsspam
Jan 25 07:56:58 lnxmail61 sshd[9207]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.211.6.65
2020-01-25 16:00:18
91.188.223.249 attackbots
Unauthorized connection attempt detected from IP address 91.188.223.249 to port 2220 [J]
2020-01-25 16:39:54
31.42.173.53 attackbotsspam
20/1/24@23:52:39: FAIL: Alarm-Network address from=31.42.173.53
20/1/24@23:52:39: FAIL: Alarm-Network address from=31.42.173.53
...
2020-01-25 16:05:10
67.182.97.168 attackbotsspam
Unauthorized connection attempt detected from IP address 67.182.97.168 to port 2220 [J]
2020-01-25 16:29:58
106.79.224.138 attackbotsspam
ENG,WP GET /wp-login.php
2020-01-25 16:19:48
134.209.16.36 attack
Jan 25 08:54:57 * sshd[19992]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.16.36
Jan 25 08:54:58 * sshd[19992]: Failed password for invalid user test from 134.209.16.36 port 49416 ssh2
2020-01-25 16:26:08
200.54.51.124 attackbotsspam
Jan 25 09:33:08 pkdns2 sshd\[55649\]: Failed password for root from 200.54.51.124 port 50098 ssh2Jan 25 09:35:57 pkdns2 sshd\[55843\]: Failed password for root from 200.54.51.124 port 41232 ssh2Jan 25 09:38:48 pkdns2 sshd\[56038\]: Invalid user oradev from 200.54.51.124Jan 25 09:38:49 pkdns2 sshd\[56038\]: Failed password for invalid user oradev from 200.54.51.124 port 60980 ssh2Jan 25 09:41:35 pkdns2 sshd\[56198\]: Invalid user teamspeak from 200.54.51.124Jan 25 09:41:37 pkdns2 sshd\[56198\]: Failed password for invalid user teamspeak from 200.54.51.124 port 53066 ssh2
...
2020-01-25 16:16:16

Recently Reported IPs

134.119.0.131 104.21.94.189 134.117.27.24 134.119.0.104
134.119.0.36 134.119.0.181 134.119.0.41 134.106.87.73
134.119.0.32 134.119.0.22 134.119.0.30 134.119.0.141
134.119.0.42 104.21.94.208 134.119.0.8 134.119.0.57
134.119.0.82 134.119.100.223 134.119.105.198 134.119.116.121