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

Region: North Rhine-Westphalia

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

;; QUESTION SECTION:
;137.226.100.99.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 13 08:45:57 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 99.100.226.137.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 99.100.226.137.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.23.224.121 attackbots
103.23.224.121 - - [08/Nov/2019:15:37:12 +0100] "POST /wp-login.php HTTP/1.1" 200 2112 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
103.23.224.121 - - [08/Nov/2019:15:37:14 +0100] "POST /wp-login.php HTTP/1.1" 200 2093 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-11-09 01:59:04
159.89.10.77 attackspambots
2019-11-08T17:55:20.561088abusebot-5.cloudsearch.cf sshd\[2463\]: Invalid user applmgr from 159.89.10.77 port 39158
2019-11-09 02:06:20
212.64.27.53 attackspambots
Nov  8 18:03:21 microserver sshd[7435]: Invalid user vps from 212.64.27.53 port 58906
Nov  8 18:03:21 microserver sshd[7435]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.27.53
Nov  8 18:03:22 microserver sshd[7435]: Failed password for invalid user vps from 212.64.27.53 port 58906 ssh2
Nov  8 18:09:46 microserver sshd[8146]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.27.53  user=root
Nov  8 18:09:48 microserver sshd[8146]: Failed password for root from 212.64.27.53 port 49784 ssh2
Nov  8 18:30:16 microserver sshd[11152]: Invalid user matt from 212.64.27.53 port 41168
Nov  8 18:30:16 microserver sshd[11152]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.27.53
Nov  8 18:30:18 microserver sshd[11152]: Failed password for invalid user matt from 212.64.27.53 port 41168 ssh2
Nov  8 18:37:06 microserver sshd[11947]: Invalid user epmd from 212.64.27.53 port 44714
Nov
2019-11-09 02:04:11
125.124.70.22 attackspambots
Nov  8 08:00:56 auw2 sshd\[22447\]: Invalid user support from 125.124.70.22
Nov  8 08:00:56 auw2 sshd\[22447\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.124.70.22
Nov  8 08:00:58 auw2 sshd\[22447\]: Failed password for invalid user support from 125.124.70.22 port 46146 ssh2
Nov  8 08:05:46 auw2 sshd\[22880\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.124.70.22  user=root
Nov  8 08:05:48 auw2 sshd\[22880\]: Failed password for root from 125.124.70.22 port 56904 ssh2
2019-11-09 02:29:32
92.119.160.52 attackspambots
92.119.160.52 was recorded 54 times by 15 hosts attempting to connect to the following ports: 26106,26081,54592,44939,25670,47142,51557,39814,42714,56055,43621,49289,45661,29825,60656,42987,39486,28497,28843,48148,27137,55029,27403,55979,50103,63034,63694,55792,65055,29228,59557,29528. Incident counter (4h, 24h, all-time): 54, 326, 441
2019-11-09 02:03:58
107.172.108.142 attackbotsspam
Nov  8 15:05:00 spandau postfix/smtpd[7513]: warning: hostname yellowpages.com does not resolve to address 107.172.108.142
Nov  8 15:05:00 spandau postfix/smtpd[7513]: connect from unknown[107.172.108.142]
Nov x@x
Nov  8 15:05:02 spandau postfix/smtpd[7513]: disconnect from unknown[107.172.108.142]
Nov  8 15:34:10 spandau postfix/smtpd[8165]: warning: hostname yellowpages.com does not resolve to address 107.172.108.142
Nov  8 15:34:10 spandau postfix/smtpd[8165]: connect from unknown[107.172.108.142]
Nov x@x
Nov  8 15:34:12 spandau postfix/smtpd[8165]: disconnect from unknown[107.172.108.142]
Nov  8 15:36:57 spandau postfix/smtpd[9300]: warning: hostname yellowpages.com does not resolve to address 107.172.108.142
Nov  8 15:36:57 spandau postfix/smtpd[9300]: connect from unknown[107.172.108.142]
Nov x@x
Nov  8 15:36:58 spandau postfix/smtpd[9300]: disconnect from unknown[107.172.108.142]
Nov  8 15:39:34 spandau postfix/smtpd[9463]: warning: hostname yellowpages.com does ........
-------------------------------
2019-11-09 02:17:58
113.171.23.119 attack
IP attempted unauthorised action
2019-11-09 02:18:43
153.122.144.121 attackbotsspam
Nov  8 18:09:06 venus sshd\[20227\]: Invalid user 123 from 153.122.144.121 port 51641
Nov  8 18:09:06 venus sshd\[20227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=153.122.144.121
Nov  8 18:09:08 venus sshd\[20227\]: Failed password for invalid user 123 from 153.122.144.121 port 51641 ssh2
...
2019-11-09 02:25:48
81.134.41.100 attack
Nov  8 18:42:59 cavern sshd[13536]: Failed password for root from 81.134.41.100 port 55634 ssh2
2019-11-09 02:16:34
2.92.205.51 attack
Unauthorised access (Nov  8) SRC=2.92.205.51 LEN=52 TTL=116 ID=13119 DF TCP DPT=445 WINDOW=8192 SYN 
Unauthorised access (Nov  8) SRC=2.92.205.51 LEN=52 TTL=116 ID=6091 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-09 02:30:01
49.88.112.71 attack
Nov  8 18:56:07 MK-Soft-VM7 sshd[11089]: Failed password for root from 49.88.112.71 port 37979 ssh2
Nov  8 18:56:09 MK-Soft-VM7 sshd[11089]: Failed password for root from 49.88.112.71 port 37979 ssh2
...
2019-11-09 02:05:15
37.59.114.113 attackspambots
2019-11-08T17:47:24.276864abusebot-5.cloudsearch.cf sshd\[2407\]: Invalid user support from 37.59.114.113 port 35102
2019-11-09 01:55:54
222.186.175.151 attack
Nov  6 02:34:04 microserver sshd[22158]: Failed none for root from 222.186.175.151 port 19798 ssh2
Nov  6 02:34:05 microserver sshd[22158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.151  user=root
Nov  6 02:34:07 microserver sshd[22158]: Failed password for root from 222.186.175.151 port 19798 ssh2
Nov  6 02:34:11 microserver sshd[22158]: Failed password for root from 222.186.175.151 port 19798 ssh2
Nov  6 02:34:15 microserver sshd[22158]: Failed password for root from 222.186.175.151 port 19798 ssh2
Nov  6 10:38:18 microserver sshd[20211]: Failed none for root from 222.186.175.151 port 44726 ssh2
Nov  6 10:38:19 microserver sshd[20211]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.151  user=root
Nov  6 10:38:21 microserver sshd[20211]: Failed password for root from 222.186.175.151 port 44726 ssh2
Nov  6 10:38:25 microserver sshd[20211]: Failed password for root from 222.186.175.151 port 44726 ssh2
2019-11-09 02:25:26
222.186.175.212 attackbotsspam
2019-09-23 07:07:55,048 fail2ban.actions        [818]: NOTICE  [sshd] Ban 222.186.175.212
2019-09-23 21:33:17,723 fail2ban.actions        [818]: NOTICE  [sshd] Ban 222.186.175.212
2019-09-24 12:06:23,634 fail2ban.actions        [818]: NOTICE  [sshd] Ban 222.186.175.212
...
2019-11-09 02:31:22
78.186.138.134 attack
" "
2019-11-09 02:15:35

Recently Reported IPs

137.226.98.52 137.226.100.124 137.226.101.28 137.226.101.81
137.226.101.30 137.226.102.242 137.226.103.55 137.226.136.134
137.226.132.0 137.226.141.115 137.226.141.100 137.226.8.32
137.226.145.218 137.226.146.224 137.226.150.190 137.226.151.145
137.226.151.181 137.226.151.230 137.226.152.1 137.226.152.41