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: South Africa

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

;; QUESTION SECTION:
;105.213.109.56.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 16:16:28 CST 2022
;; MSG SIZE  rcvd: 107
Host info
56.109.213.105.in-addr.arpa domain name pointer 105-213-109-56.access.mtnbusiness.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
56.109.213.105.in-addr.arpa	name = 105-213-109-56.access.mtnbusiness.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
223.27.234.253 attackspam
Jun 29 02:27:12 server01 sshd\[18284\]: Invalid user ubuntu from 223.27.234.253
Jun 29 02:27:12 server01 sshd\[18284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.27.234.253
Jun 29 02:27:14 server01 sshd\[18284\]: Failed password for invalid user ubuntu from 223.27.234.253 port 57232 ssh2
...
2019-06-29 07:32:14
52.170.7.159 attackbots
SSH Brute-Force attacks
2019-06-29 07:47:15
185.3.111.202 attackspam
Jun 29 00:26:40 localhost sshd\[20601\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.3.111.202  user=root
Jun 29 00:26:42 localhost sshd\[20601\]: Failed password for root from 185.3.111.202 port 38565 ssh2
...
2019-06-29 07:43:25
134.209.243.95 attack
Jun 28 19:25:44 Tower sshd[3299]: Connection from 134.209.243.95 port 51356 on 192.168.10.220 port 22
Jun 28 19:25:45 Tower sshd[3299]: Invalid user transfer from 134.209.243.95 port 51356
Jun 28 19:25:45 Tower sshd[3299]: error: Could not get shadow information for NOUSER
Jun 28 19:25:45 Tower sshd[3299]: Failed password for invalid user transfer from 134.209.243.95 port 51356 ssh2
Jun 28 19:25:45 Tower sshd[3299]: Received disconnect from 134.209.243.95 port 51356:11: Bye Bye [preauth]
Jun 28 19:25:45 Tower sshd[3299]: Disconnected from invalid user transfer 134.209.243.95 port 51356 [preauth]
2019-06-29 07:59:26
58.240.111.50 attack
failed_logins
2019-06-29 07:49:24
5.196.7.123 attack
Jun 29 01:36:43 mail sshd\[23607\]: Invalid user nao from 5.196.7.123 port 33220
Jun 29 01:36:43 mail sshd\[23607\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.7.123
Jun 29 01:36:44 mail sshd\[23607\]: Failed password for invalid user nao from 5.196.7.123 port 33220 ssh2
Jun 29 01:38:12 mail sshd\[23755\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.7.123  user=mysql
Jun 29 01:38:15 mail sshd\[23755\]: Failed password for mysql from 5.196.7.123 port 49974 ssh2
2019-06-29 07:50:37
202.130.82.67 attack
vps1:sshd-InvalidUser
2019-06-29 08:03:32
177.130.138.225 attack
SMTP-sasl brute force
...
2019-06-29 07:54:58
119.28.50.163 attackspam
SSH invalid-user multiple login attempts
2019-06-29 08:11:52
37.187.176.14 attackspambots
ssh failed login
2019-06-29 08:00:37
46.101.88.10 attack
Jun 28 23:04:43 XXX sshd[1155]: Invalid user nagios from 46.101.88.10 port 10816
2019-06-29 08:08:37
184.168.27.36 attackbotsspam
184.168.27.36 - - [28/Jun/2019:14:16:14 -0500] "GET /new/wp-includes/wlwmanifest.xml HTTP/1.1" 301 258 - "-" "-"
2019-06-29 08:06:44
185.53.88.45 attackbotsspam
\[2019-06-28 19:37:38\] SECURITY\[1857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-06-28T19:37:38.734-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="9011441217900519",SessionID="0x7fc42417ead8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.53.88.45/50571",ACLName="no_extension_match"
\[2019-06-28 19:40:08\] SECURITY\[1857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-06-28T19:40:08.201-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="011441217900519",SessionID="0x7fc42430b1a8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.53.88.45/56504",ACLName="no_extension_match"
\[2019-06-28 19:42:43\] SECURITY\[1857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-06-28T19:42:43.554-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="9011441217900519",SessionID="0x7fc42417ead8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.53.88.45/56063",ACLName="no_exte
2019-06-29 07:55:17
115.52.200.221 attack
1024/tcp 1024/tcp
[2019-06-26/28]2pkt
2019-06-29 07:55:59
103.205.5.34 attackbots
Jun 26 01:11:05 HOSTNAME sshd[1384]: User r.r from 103.205.5.34 not allowed because not listed in AllowUsers
Jun 26 01:11:05 HOSTNAME sshd[1384]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.205.5.34  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=103.205.5.34
2019-06-29 07:52:20

Recently Reported IPs

105.213.109.44 105.213.109.49 105.213.109.71 105.213.110.102
105.213.109.94 105.213.110.106 105.213.110.113 105.213.110.124
105.213.110.142 105.213.110.152 105.213.110.178 105.213.110.16
105.213.110.184 105.213.110.151 105.213.110.189 105.213.110.195
105.213.110.190 105.213.110.214 105.213.110.220 105.213.110.196