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

Region: Almaty

Country: Kazakhstan

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;2.74.138.99.			IN	A

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

;; Query time: 107 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 02 13:07:37 CST 2020
;; MSG SIZE  rcvd: 115
Host info
99.138.74.2.in-addr.arpa domain name pointer 2-74-138-99.kcell.kz.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
99.138.74.2.in-addr.arpa	name = 2-74-138-99.kcell.kz.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.173.183 attackspam
Nov 10 17:35:27 amit sshd\[16573\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.183  user=root
Nov 10 17:35:29 amit sshd\[16573\]: Failed password for root from 222.186.173.183 port 53214 ssh2
Nov 10 17:40:46 amit sshd\[16668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.183  user=root
...
2019-11-11 00:41:14
5.56.135.88 attackspam
5.56.135.88 - - [10/Nov/2019:15:45:54 +0100] "GET /wp-login.php HTTP/1.1" 302 536
...
2019-11-11 00:13:15
59.153.240.205 attack
Unauthorized connection attempt from IP address 59.153.240.205 on Port 445(SMB)
2019-11-11 00:10:52
171.224.204.195 attackbotsspam
Unauthorized connection attempt from IP address 171.224.204.195 on Port 445(SMB)
2019-11-11 00:11:26
201.217.155.180 attackspambots
port scan and connect, tcp 22 (ssh)
2019-11-11 00:16:29
80.82.77.33 attack
11/10/2019-17:10:34.230432 80.82.77.33 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-11-11 00:19:48
203.190.154.109 attackspam
Nov 10 06:23:12 tdfoods sshd\[24969\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.auctusglobal.com  user=root
Nov 10 06:23:14 tdfoods sshd\[24969\]: Failed password for root from 203.190.154.109 port 45374 ssh2
Nov 10 06:27:37 tdfoods sshd\[26091\]: Invalid user superpipes from 203.190.154.109
Nov 10 06:27:37 tdfoods sshd\[26091\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.auctusglobal.com
Nov 10 06:27:39 tdfoods sshd\[26091\]: Failed password for invalid user superpipes from 203.190.154.109 port 54964 ssh2
2019-11-11 00:38:30
94.233.65.130 attackbotsspam
Nov 10 15:31:46 h2022099 sshd[1880]: reveeclipse mapping checking getaddrinfo for dsl-94-233-65-130.avtlg.ru [94.233.65.130] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 10 15:31:46 h2022099 sshd[1880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.233.65.130  user=r.r
Nov 10 15:31:48 h2022099 sshd[1880]: Failed password for r.r from 94.233.65.130 port 50315 ssh2
Nov 10 15:31:56 h2022099 sshd[1880]: Failed password for r.r from 94.233.65.130 port 50315 ssh2
Nov 10 15:31:57 h2022099 sshd[1880]: Failed password for r.r from 94.233.65.130 port 50315 ssh2
Nov 10 15:31:57 h2022099 sshd[1880]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.233.65.130  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=94.233.65.130
2019-11-11 00:08:07
89.172.51.36 attack
Nov 10 15:31:00 mxgate1 postfix/postscreen[20780]: CONNECT from [89.172.51.36]:13304 to [176.31.12.44]:25
Nov 10 15:31:00 mxgate1 postfix/dnsblog[20783]: addr 89.172.51.36 listed by domain zen.spamhaus.org as 127.0.0.11
Nov 10 15:31:00 mxgate1 postfix/dnsblog[20783]: addr 89.172.51.36 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 10 15:31:00 mxgate1 postfix/dnsblog[20785]: addr 89.172.51.36 listed by domain bl.spamcop.net as 127.0.0.2
Nov 10 15:31:00 mxgate1 postfix/dnsblog[20782]: addr 89.172.51.36 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Nov 10 15:31:00 mxgate1 postfix/dnsblog[20784]: addr 89.172.51.36 listed by domain b.barracudacentral.org as 127.0.0.2
Nov 10 15:31:00 mxgate1 postfix/dnsblog[20781]: addr 89.172.51.36 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 10 15:31:06 mxgate1 postfix/postscreen[20780]: DNSBL rank 6 for [89.172.51.36]:13304
Nov x@x
Nov 10 15:31:08 mxgate1 postfix/postscreen[20780]: HANGUP after 2.4 from [89.172.51.36]:13304 in........
-------------------------------
2019-11-11 00:05:07
61.191.130.198 attackspam
Brute force attempt
2019-11-11 00:28:22
132.148.135.229 attackbotsspam
Automatic report - XMLRPC Attack
2019-11-11 00:42:57
201.49.110.210 attackspam
Nov 10 16:05:56 game-panel sshd[9617]: Failed password for root from 201.49.110.210 port 36144 ssh2
Nov 10 16:10:22 game-panel sshd[9869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.49.110.210
Nov 10 16:10:24 game-panel sshd[9869]: Failed password for invalid user gdm from 201.49.110.210 port 45944 ssh2
2019-11-11 00:25:24
173.212.202.169 attackspam
Lines containing failures of 173.212.202.169 (max 1000)
Nov  9 00:57:09 Server sshd[6800]: Did not receive identification string from 173.212.202.169 port 37324
Nov  9 01:00:50 Server sshd[6805]: User r.r from 173.212.202.169 not allowed because not listed in AllowUsers
Nov  9 01:00:50 Server sshd[6805]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.212.202.169  user=r.r
Nov  9 01:00:50 Server sshd[6803]: User r.r from 173.212.202.169 not allowed because not listed in AllowUsers
Nov  9 01:00:50 Server sshd[6803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.212.202.169  user=r.r
Nov  9 01:00:50 Server sshd[6814]: Invalid user jira from 173.212.202.169 port 42930
Nov  9 01:00:50 Server sshd[6809]: Invalid user test from 173.212.202.169 port 41166
Nov  9 01:00:50 Server sshd[6807]: User r.r from 173.212.202.169 not allowed because not listed in AllowUsers
Nov  9 01:00:50 Server ssh........
------------------------------
2019-11-11 00:29:27
178.44.192.35 attack
19/11/10@09:45:58: FAIL: Alarm-Intrusion address from=178.44.192.35
19/11/10@09:45:59: FAIL: Alarm-Intrusion address from=178.44.192.35
...
2019-11-11 00:06:33
86.105.53.166 attack
Nov 10 16:47:19 vps691689 sshd[24420]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.105.53.166
Nov 10 16:47:20 vps691689 sshd[24420]: Failed password for invalid user guest from 86.105.53.166 port 35071 ssh2
Nov 10 16:50:24 vps691689 sshd[24527]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.105.53.166
...
2019-11-11 00:03:37

Recently Reported IPs

145.60.120.213 57.182.183.12 209.242.221.242 209.242.221.123
201.161.58.221 200.94.242.147 247.75.156.34 204.109.110.51
104.244.228.26 61.190.123.15 114.143.115.70 223.155.45.127
107.60.3.67 44.251.34.78 46.224.203.240 203.73.21.140
110.223.127.204 172.113.118.120 14.177.235.24 168.10.208.143