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

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

;; QUESTION SECTION:
;89.142.101.104.			IN	A

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

;; Query time: 141 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 15:28:55 CST 2025
;; MSG SIZE  rcvd: 107
Host info
104.101.142.89.in-addr.arpa domain name pointer BSN-142-101-104.dynamic.siol.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
104.101.142.89.in-addr.arpa	name = BSN-142-101-104.dynamic.siol.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
60.215.189.242 attack
5500/tcp
[2019-06-21]1pkt
2019-06-22 06:38:19
36.66.111.57 attackbotsspam
Request: "GET / HTTP/1.1"
2019-06-22 06:48:40
186.17.190.232 attackspambots
fail2ban honeypot
2019-06-22 06:43:14
81.22.45.26 attack
port scan/probe/communication attempt
2019-06-22 07:02:07
104.129.58.202 attackbots
NAME : QUADRANET-ATLANTA CIDR : 104.129.24.0/23 | STATUS : 200 ROBOT {Looking for resource vulnerabilities} DDoS Attack USA - Georgia - block certain countries :) IP: 104.129.58.202  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-06-22 06:34:28
187.60.46.134 attack
SPF Fail sender not permitted to send mail for @lombardiplants.it / Mail sent to address hacked/leaked from Destructoid
2019-06-22 06:28:37
80.227.12.38 attackspambots
2019-06-21T21:41:40.658808  sshd[30142]: Invalid user san from 80.227.12.38 port 47100
2019-06-21T21:41:40.674684  sshd[30142]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.227.12.38
2019-06-21T21:41:40.658808  sshd[30142]: Invalid user san from 80.227.12.38 port 47100
2019-06-21T21:41:42.570915  sshd[30142]: Failed password for invalid user san from 80.227.12.38 port 47100 ssh2
2019-06-21T21:43:28.402216  sshd[30157]: Invalid user zhui from 80.227.12.38 port 35978
...
2019-06-22 06:44:35
125.72.228.30 attack
23/tcp 23/tcp 23/tcp
[2019-06-21]3pkt
2019-06-22 07:07:10
185.176.27.42 attackbotsspam
firewall-block, port(s): 1208/tcp, 1210/tcp, 1571/tcp, 2484/tcp, 2690/tcp
2019-06-22 06:30:44
218.92.0.175 attackbots
Trying ports that it shouldn't be.
2019-06-22 06:58:57
41.203.78.215 attackbotsspam
Jun 21 21:23:20 mxgate1 postfix/postscreen[20865]: CONNECT from [41.203.78.215]:37411 to [176.31.12.44]:25
Jun 21 21:23:20 mxgate1 postfix/dnsblog[21673]: addr 41.203.78.215 listed by domain cbl.abuseat.org as 127.0.0.2
Jun 21 21:23:20 mxgate1 postfix/dnsblog[21672]: addr 41.203.78.215 listed by domain zen.spamhaus.org as 127.0.0.3
Jun 21 21:23:20 mxgate1 postfix/dnsblog[21672]: addr 41.203.78.215 listed by domain zen.spamhaus.org as 127.0.0.4
Jun 21 21:23:20 mxgate1 postfix/dnsblog[21676]: addr 41.203.78.215 listed by domain bl.spamcop.net as 127.0.0.2
Jun 21 21:23:20 mxgate1 postfix/dnsblog[21675]: addr 41.203.78.215 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 21 21:23:26 mxgate1 postfix/postscreen[20865]: DNSBL rank 5 for [41.203.78.215]:37411
Jun x@x
Jun 21 21:23:27 mxgate1 postfix/postscreen[20865]: DISCONNECT [41.203.78.215]:37411


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=41.203.78.215
2019-06-22 07:08:55
201.1.81.21 attack
Request: "GET / HTTP/1.1" Request: "GET / HTTP/1.1"
2019-06-22 06:56:39
190.201.160.70 attackbotsspam
Jun 21 12:25:34 sanyalnet-awsem3-1 sshd[20198]: Connection from 190.201.160.70 port 52124 on 172.30.0.184 port 22
Jun 21 12:25:34 sanyalnet-awsem3-1 sshd[20199]: Connection from 190.201.160.70 port 52126 on 172.30.0.184 port 22
Jun 21 12:25:34 sanyalnet-awsem3-1 sshd[20199]: Invalid user pi from 190.201.160.70
Jun 21 12:25:34 sanyalnet-awsem3-1 sshd[20198]: Invalid user pi from 190.201.160.70
Jun 21 12:25:35 sanyalnet-awsem3-1 sshd[20199]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.201.160.70 
Jun 21 12:25:35 sanyalnet-awsem3-1 sshd[20198]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.201.160.70 
Jun 21 12:25:36 sanyalnet-awsem3-1 sshd[20199]: Failed none for invalid user pi from 190.201.160.70 port 52126 ssh2
Jun 21 12:25:36 sanyalnet-awsem3-1 sshd[20198]: Failed none for invalid user pi from 190.201.160.70 port 52124 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.
2019-06-22 06:44:20
86.243.239.95 attackspambots
23/tcp
[2019-06-21]1pkt
2019-06-22 06:46:21
36.238.88.155 attack
37215/tcp
[2019-06-21]1pkt
2019-06-22 07:09:25

Recently Reported IPs

9.152.233.66 129.247.18.181 107.176.215.51 4.188.175.202
214.176.69.238 204.188.66.41 100.92.24.160 202.224.108.251
176.3.142.254 17.10.59.209 64.130.90.179 136.248.1.73
134.131.151.228 190.35.109.203 249.73.214.176 22.55.198.124
161.225.150.217 44.252.141.146 4.26.136.169 71.144.217.170