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

;; QUESTION SECTION:
;137.226.244.145.		IN	A

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

;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 27 02:20:28 CST 2022
;; MSG SIZE  rcvd: 108
Host info
145.244.226.137.in-addr.arpa domain name pointer spike.informatik.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
145.244.226.137.in-addr.arpa	name = spike.informatik.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
193.32.160.142 attackbots
Aug 28 23:26:30 relay postfix/smtpd\[15937\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.142\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.139\]\>
Aug 28 23:26:30 relay postfix/smtpd\[15937\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.142\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.139\]\>
Aug 28 23:26:30 relay postfix/smtpd\[15937\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.142\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.139\]\>
Aug 28 23:26:30 relay postfix/smtpd\[15937\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.142\]: 554 5.7.1 \: Relay access denied\; from=\
2019-08-29 07:15:35
177.124.216.10 attackspam
Aug 29 00:22:06 ubuntu-2gb-nbg1-dc3-1 sshd[16574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.124.216.10
Aug 29 00:22:08 ubuntu-2gb-nbg1-dc3-1 sshd[16574]: Failed password for invalid user 123 from 177.124.216.10 port 59186 ssh2
...
2019-08-29 07:21:40
36.230.90.84 attackbotsspam
23/tcp
[2019-08-28]1pkt
2019-08-29 07:45:21
82.209.198.252 attackspam
Caught in portsentry honeypot
2019-08-29 07:34:22
206.81.24.126 attackbotsspam
2019-08-28T22:55:04.612622abusebot-2.cloudsearch.cf sshd\[29474\]: Invalid user operador from 206.81.24.126 port 57008
2019-08-28T22:55:04.617204abusebot-2.cloudsearch.cf sshd\[29474\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.81.24.126
2019-08-29 07:25:48
116.196.120.101 attackspambots
Aug 28 21:22:12 OPSO sshd\[20139\]: Invalid user ircbot from 116.196.120.101 port 53843
Aug 28 21:22:12 OPSO sshd\[20139\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.196.120.101
Aug 28 21:22:14 OPSO sshd\[20139\]: Failed password for invalid user ircbot from 116.196.120.101 port 53843 ssh2
Aug 28 21:24:06 OPSO sshd\[20397\]: Invalid user river from 116.196.120.101 port 35040
Aug 28 21:24:06 OPSO sshd\[20397\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.196.120.101
2019-08-29 07:39:51
185.173.35.13 attack
firewall-block, port(s): 5632/udp
2019-08-29 07:20:57
206.189.200.132 attack
Aug 29 01:03:53 dedicated sshd[7947]: Invalid user User from 206.189.200.132 port 33466
2019-08-29 07:23:35
122.14.219.4 attackspam
Failed password for invalid user ronald from 122.14.219.4 port 35158 ssh2
Invalid user travis from 122.14.219.4 port 60822
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.14.219.4
Failed password for invalid user travis from 122.14.219.4 port 60822 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.14.219.4  user=root
2019-08-29 07:35:07
140.224.142.7 attack
$f2bV_matches
2019-08-29 07:12:04
139.59.80.65 attackspambots
(sshd) Failed SSH login from 139.59.80.65 (-): 5 in the last 3600 secs
2019-08-29 07:41:39
79.126.90.245 attackbotsspam
Aug 28 15:57:44 mxgate1 postfix/postscreen[19155]: CONNECT from [79.126.90.245]:21346 to [176.31.12.44]:25
Aug 28 15:57:44 mxgate1 postfix/dnsblog[19159]: addr 79.126.90.245 listed by domain zen.spamhaus.org as 127.0.0.11
Aug 28 15:57:44 mxgate1 postfix/dnsblog[19159]: addr 79.126.90.245 listed by domain zen.spamhaus.org as 127.0.0.4
Aug 28 15:57:44 mxgate1 postfix/dnsblog[19159]: addr 79.126.90.245 listed by domain zen.spamhaus.org as 127.0.0.3
Aug 28 15:57:44 mxgate1 postfix/dnsblog[19157]: addr 79.126.90.245 listed by domain cbl.abuseat.org as 127.0.0.2
Aug 28 15:57:44 mxgate1 postfix/dnsblog[19158]: addr 79.126.90.245 listed by domain bl.spamcop.net as 127.0.0.2
Aug 28 15:57:44 mxgate1 postfix/dnsblog[19160]: addr 79.126.90.245 listed by domain b.barracudacentral.org as 127.0.0.2
Aug 28 15:57:50 mxgate1 postfix/postscreen[19155]: DNSBL rank 5 for [79.126.90.245]:21346
Aug x@x
Aug 28 15:57:51 mxgate1 postfix/postscreen[19155]: HANGUP after 1.1 from [79.126.90.245]:21........
-------------------------------
2019-08-29 07:33:22
45.125.140.134 attackbots
firewall-block, port(s): 5431/tcp
2019-08-29 07:43:51
76.183.84.74 attack
Aug 29 00:44:09 yabzik sshd[14932]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=76.183.84.74
Aug 29 00:44:11 yabzik sshd[14932]: Failed password for invalid user sara from 76.183.84.74 port 49632 ssh2
Aug 29 00:49:06 yabzik sshd[16613]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=76.183.84.74
2019-08-29 07:38:14
106.13.104.94 attackspam
Aug 28 20:14:34 [munged] sshd[17268]: Invalid user vishvjit from 106.13.104.94 port 38867
Aug 28 20:14:34 [munged] sshd[17268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.104.94
2019-08-29 07:19:33

Recently Reported IPs

180.76.139.68 137.226.173.55 137.226.234.246 180.76.0.209
169.229.170.88 180.76.148.218 137.226.199.62 169.229.200.175
169.229.174.231 169.229.70.216 169.229.70.230 169.229.70.233
169.229.70.242 169.229.71.4 169.229.71.5 169.229.71.14
169.229.71.24 169.229.71.249 169.229.71.250 169.229.71.255