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

;; QUESTION SECTION:
;105.13.12.155.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:04:03 CST 2023
;; MSG SIZE  rcvd: 106
Host info
Host 155.12.13.105.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 155.12.13.105.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
181.130.115.77 attackspambots
Unauthorized connection attempt detected from IP address 181.130.115.77 to port 2220 [J]
2020-01-12 22:05:38
185.25.51.215 attackbotsspam
Jan 12 13:08:11 vlre-nyc-1 sshd\[26512\]: Invalid user postgres from 185.25.51.215
Jan 12 13:08:11 vlre-nyc-1 sshd\[26512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.25.51.215
Jan 12 13:08:12 vlre-nyc-1 sshd\[26512\]: Failed password for invalid user postgres from 185.25.51.215 port 37748 ssh2
Jan 12 13:13:11 vlre-nyc-1 sshd\[26575\]: Invalid user vivek from 185.25.51.215
Jan 12 13:13:11 vlre-nyc-1 sshd\[26575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.25.51.215
...
2020-01-12 21:40:38
198.211.114.102 attackbots
Unauthorized connection attempt detected from IP address 198.211.114.102 to port 2220 [J]
2020-01-12 22:03:10
139.199.115.210 attack
Unauthorized connection attempt detected from IP address 139.199.115.210 to port 2220 [J]
2020-01-12 22:11:51
187.177.164.200 attack
Unauthorized connection attempt detected from IP address 187.177.164.200 to port 23 [J]
2020-01-12 21:38:22
91.165.42.209 attackspambots
Unauthorized connection attempt detected from IP address 91.165.42.209 to port 23 [J]
2020-01-12 22:17:33
196.218.45.172 attackspam
Unauthorized connection attempt detected from IP address 196.218.45.172 to port 23 [J]
2020-01-12 22:04:10
36.41.174.139 attackspam
Unauthorized connection attempt detected from IP address 36.41.174.139 to port 2220 [J]
2020-01-12 22:23:20
170.106.37.194 attack
Unauthorized connection attempt detected from IP address 170.106.37.194 to port 3001 [J]
2020-01-12 22:08:12
177.104.16.51 attackspambots
Unauthorized connection attempt detected from IP address 177.104.16.51 to port 80 [J]
2020-01-12 21:42:11
104.131.22.150 attackbots
Unauthorized connection attempt detected from IP address 104.131.22.150 to port 2220 [J]
2020-01-12 22:14:47
31.167.139.189 attack
Unauthorized connection attempt detected from IP address 31.167.139.189 to port 1433 [J]
2020-01-12 22:23:38
82.78.223.249 attackbotsspam
Unauthorized connection attempt detected from IP address 82.78.223.249 to port 8080 [J]
2020-01-12 21:54:09
156.218.210.134 attackbotsspam
Unauthorized connection attempt detected from IP address 156.218.210.134 to port 23 [J]
2020-01-12 22:09:23
78.187.224.112 attackspam
Unauthorized connection attempt detected from IP address 78.187.224.112 to port 80 [J]
2020-01-12 21:55:14

Recently Reported IPs

105.129.247.192 105.13.121.80 105.129.75.147 105.129.87.52
105.129.235.204 105.13.171.224 105.13.135.101 105.173.23.129
105.13.113.70 105.129.35.186 105.129.187.0 105.13.114.147
105.129.233.123 105.129.44.124 105.129.181.109 105.129.39.31
105.129.174.244 105.129.163.57 105.129.225.173 105.129.230.2