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

;; QUESTION SECTION:
;134.28.200.130.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 20:19:42 CST 2025
;; MSG SIZE  rcvd: 107
Host info
130.200.28.134.in-addr.arpa domain name pointer l00p00.rz.tu-harburg.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
130.200.28.134.in-addr.arpa	name = l00p00.rz.tu-harburg.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
51.68.231.147 attackspam
Reported by AbuseIPDB proxy server.
2019-07-31 07:34:15
58.219.130.203 attackbotsspam
Jul 31 00:42:44 tux-35-217 sshd\[32048\]: Invalid user nexthink from 58.219.130.203 port 51237
Jul 31 00:42:45 tux-35-217 sshd\[32048\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.219.130.203
Jul 31 00:42:46 tux-35-217 sshd\[32048\]: Failed password for invalid user nexthink from 58.219.130.203 port 51237 ssh2
Jul 31 00:42:54 tux-35-217 sshd\[32050\]: Invalid user plexuser from 58.219.130.203 port 54293
...
2019-07-31 07:32:26
151.70.15.109 attack
Automatic report - Port Scan Attack
2019-07-31 07:39:39
204.8.156.142 attackspambots
Jul 31 00:42:32 MainVPS sshd[26759]: Invalid user NetLinx from 204.8.156.142 port 54912
Jul 31 00:42:32 MainVPS sshd[26759]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=204.8.156.142
Jul 31 00:42:32 MainVPS sshd[26759]: Invalid user NetLinx from 204.8.156.142 port 54912
Jul 31 00:42:33 MainVPS sshd[26759]: Failed password for invalid user NetLinx from 204.8.156.142 port 54912 ssh2
Jul 31 00:42:32 MainVPS sshd[26759]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=204.8.156.142
Jul 31 00:42:32 MainVPS sshd[26759]: Invalid user NetLinx from 204.8.156.142 port 54912
Jul 31 00:42:33 MainVPS sshd[26759]: Failed password for invalid user NetLinx from 204.8.156.142 port 54912 ssh2
Jul 31 00:42:34 MainVPS sshd[26759]: Disconnecting invalid user NetLinx 204.8.156.142 port 54912: Change of username or service not allowed: (NetLinx,ssh-connection) -> (administrator,ssh-connection [preauth]
...
2019-07-31 07:42:39
134.209.100.31 attackbots
2019-07-30T23:53:27.826417abusebot.cloudsearch.cf sshd\[26586\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.100.31  user=ftp
2019-07-31 07:57:24
168.228.149.185 attack
failed_logins
2019-07-31 08:05:56
45.5.102.166 attackspam
DATE:2019-07-31 00:42:41, IP:45.5.102.166, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-07-31 07:40:15
113.194.131.234 attack
2019-07-31T00:42:45.706075stark.klein-stark.info sshd\[15135\]: Invalid user admin from 113.194.131.234 port 53483
2019-07-31T00:42:45.711817stark.klein-stark.info sshd\[15135\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.194.131.234
2019-07-31T00:42:47.243595stark.klein-stark.info sshd\[15135\]: Failed password for invalid user admin from 113.194.131.234 port 53483 ssh2
...
2019-07-31 07:34:38
124.156.211.107 attackbotsspam
firewall-block, port(s): 4433/tcp
2019-07-31 07:58:36
46.101.142.238 attack
WordPress (CMS) attack attempts.
Date: 2019 Jul 30. 23:17:54
Source IP: 46.101.142.238

Portion of the log(s):
46.101.142.238 - [30/Jul/2019:23:17:53 +0200] "POST /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
46.101.142.238 - [30/Jul/2019:23:17:53 +0200] "GET /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
46.101.142.238 - [30/Jul/2019:23:17:53 +0200] "POST /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
46.101.142.238 - [30/Jul/2019:23:17:53 +0200] "GET /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
46.101.142.238 - [30/Jul/2019:23:17:53 +0200] "POST /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-31 07:31:53
80.82.77.240 attackspambots
30.07.2019 22:43:06 Connection to port 6697 blocked by firewall
2019-07-31 07:27:15
159.65.127.70 attackspam
st-nyc1-01 recorded 3 login violations from 159.65.127.70 and was blocked at 2019-07-30 23:16:58. 159.65.127.70 has been blocked on 9 previous occasions. 159.65.127.70's first attempt was recorded at 2019-07-30 20:42:42
2019-07-31 07:28:33
91.223.106.63 attackspam
Bruteforcing port 3389 (Remote Desktop) - Exceed maximum 10 attempts/hour
2019-07-31 07:36:03
118.97.194.110 attackbots
firewall-block, port(s): 445/tcp
2019-07-31 08:07:25
106.12.197.119 attack
Jul 31 01:24:50 dedicated sshd[7885]: Invalid user ts from 106.12.197.119 port 50952
2019-07-31 07:31:34

Recently Reported IPs

128.193.107.134 12.213.43.93 161.83.161.56 29.84.40.45
140.206.181.113 239.188.49.66 177.12.188.190 25.46.12.52
216.108.212.13 37.111.159.208 235.21.173.118 4.211.234.170
226.141.76.124 97.206.229.207 229.148.63.2 57.104.138.142
31.29.101.35 25.27.211.237 145.179.22.72 70.78.95.251