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

;; QUESTION SECTION:
;134.108.34.23.			IN	A

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

;; Query time: 104 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:01:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
23.34.108.134.in-addr.arpa domain name pointer www.haw-esslingen.de.
23.34.108.134.in-addr.arpa domain name pointer www2.hs-esslingen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
23.34.108.134.in-addr.arpa	name = www.haw-esslingen.de.
23.34.108.134.in-addr.arpa	name = www2.hs-esslingen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.48.133.54 attack
Unauthorized connection attempt detected from IP address 178.48.133.54 to port 81 [J]
2020-01-06 03:18:40
222.186.30.187 attack
Jan  6 02:30:23 lcl-usvr-02 sshd[28147]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.187  user=root
Jan  6 02:30:26 lcl-usvr-02 sshd[28147]: Failed password for root from 222.186.30.187 port 58416 ssh2
...
2020-01-06 03:35:07
200.31.247.29 attackbotsspam
Unauthorized connection attempt detected from IP address 200.31.247.29 to port 8080
2020-01-06 03:11:14
142.44.184.156 attackspam
Unauthorized connection attempt detected from IP address 142.44.184.156 to port 2220 [J]
2020-01-06 03:22:07
200.207.220.150 attack
Unauthorized connection attempt detected from IP address 200.207.220.150 to port 23
2020-01-06 03:10:23
61.77.200.15 attackbots
Unauthorized connection attempt detected from IP address 61.77.200.15 to port 5555 [J]
2020-01-06 03:31:11
177.94.13.20 attackspam
Unauthorized connection attempt detected from IP address 177.94.13.20 to port 23
2020-01-06 03:49:57
213.66.135.39 attackbotsspam
Unauthorized connection attempt detected from IP address 213.66.135.39 to port 5555
2020-01-06 03:38:06
196.52.43.60 attackspam
Unauthorized connection attempt detected from IP address 196.52.43.60 to port 199 [J]
2020-01-06 03:12:13
202.47.32.223 attackspam
Unauthorized connection attempt detected from IP address 202.47.32.223 to port 445
2020-01-06 03:38:56
187.132.27.152 attackbotsspam
Unauthorized connection attempt detected from IP address 187.132.27.152 to port 80
2020-01-06 03:15:26
183.109.210.53 attackspam
Unauthorized connection attempt detected from IP address 183.109.210.53 to port 4567 [J]
2020-01-06 03:17:22
200.236.125.93 attackbots
Unauthorized connection attempt detected from IP address 200.236.125.93 to port 23
2020-01-06 03:40:13
190.210.245.124 attackspam
Unauthorized connection attempt detected from IP address 190.210.245.124 to port 80 [J]
2020-01-06 03:13:58
220.79.147.172 attackbotsspam
Unauthorized connection attempt detected from IP address 220.79.147.172 to port 4567 [J]
2020-01-06 03:36:02

Recently Reported IPs

134.106.50.21 134.119.0.180 134.102.234.52 134.119.0.131
134.119.0.100 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