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

;; QUESTION SECTION:
;105.213.122.32.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 20:47:55 CST 2022
;; MSG SIZE  rcvd: 107
Host info
32.122.213.105.in-addr.arpa domain name pointer 105-213-122-32.access.mtnbusiness.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
32.122.213.105.in-addr.arpa	name = 105-213-122-32.access.mtnbusiness.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
207.46.151.8 attackbots
Invalid user support from 207.46.151.8 port 31068
2019-10-29 06:38:02
211.35.76.241 attackbotsspam
Invalid user test from 211.35.76.241 port 52034
2019-10-29 07:03:27
123.138.18.11 attackbots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.138.18.11  user=root
Failed password for root from 123.138.18.11 port 56668 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.138.18.11  user=root
Failed password for root from 123.138.18.11 port 50222 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.138.18.11  user=root
2019-10-29 06:45:40
210.82.30.225 attack
Invalid user admin from 210.82.30.225 port 39898
2019-10-29 06:37:40
85.214.230.105 attackspam
Invalid user il from 85.214.230.105 port 54074
2019-10-29 06:54:07
181.40.73.86 attackspambots
2019-10-28T22:57:15.633186shield sshd\[15407\]: Invalid user m@123 from 181.40.73.86 port 33629
2019-10-28T22:57:15.638455shield sshd\[15407\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.40.73.86
2019-10-28T22:57:17.973402shield sshd\[15407\]: Failed password for invalid user m@123 from 181.40.73.86 port 33629 ssh2
2019-10-28T23:01:49.119304shield sshd\[16653\]: Invalid user rfrfrfrf from 181.40.73.86 port 62240
2019-10-28T23:01:49.124544shield sshd\[16653\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.40.73.86
2019-10-29 07:07:53
185.38.3.138 attackbots
Invalid user pi from 185.38.3.138 port 49012
2019-10-29 06:41:29
121.151.153.108 attack
Invalid user helpdesk from 121.151.153.108 port 57744
2019-10-29 07:12:57
119.57.103.38 attackbots
Invalid user ts3 from 119.57.103.38 port 58109
2019-10-29 07:13:24
182.61.176.105 attack
Invalid user quevedo from 182.61.176.105 port 51676
2019-10-29 07:07:36
61.219.11.153 attack
firewall-block, port(s): 53/tcp
2019-10-29 06:56:08
182.72.178.114 attack
Invalid user shuan from 182.72.178.114 port 33420
2019-10-29 07:07:09
206.189.229.112 attackspambots
Invalid user dsj from 206.189.229.112 port 51740
2019-10-29 06:38:21
167.99.83.237 attack
Invalid user io from 167.99.83.237 port 59888
2019-10-29 07:09:38
96.251.179.98 attackspam
Invalid user developer from 96.251.179.98 port 58564
2019-10-29 06:52:39

Recently Reported IPs

105.213.122.244 105.213.122.5 105.213.122.180 105.213.122.51
105.213.122.44 105.213.122.78 105.213.122.59 105.213.122.252
105.213.122.88 105.213.122.94 105.213.122.93 105.213.122.99
101.132.143.37 105.213.123.102 105.213.123.11 105.213.123.116
105.213.123.121 105.213.123.156 105.213.123.160 105.213.123.17