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

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

;; QUESTION SECTION:
;213.145.104.175.		IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 04:33:52 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 175.104.145.213.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 175.104.145.213.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.253.171.172 attackbots
suspicious action Thu, 12 Mar 2020 11:29:22 -0300
2020-03-12 22:54:04
36.72.218.107 attackspam
Unauthorized connection attempt from IP address 36.72.218.107 on Port 445(SMB)
2020-03-12 22:45:05
49.88.112.112 attackspam
Failed password for root from 49.88.112.112 port 33219 ssh2
Failed password for root from 49.88.112.112 port 33219 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.112  user=root
Failed password for root from 49.88.112.112 port 24772 ssh2
Failed password for root from 49.88.112.112 port 24772 ssh2
2020-03-12 22:25:02
189.163.240.187 attackspam
Telnet/23 MH Probe, Scan, BF, Hack -
2020-03-12 22:52:46
106.13.63.120 attackbots
Feb 12 03:58:46 woltan sshd[17189]: Failed password for invalid user rouquette from 106.13.63.120 port 52278 ssh2
2020-03-12 23:07:13
109.237.85.33 attackbots
suspicious action Thu, 12 Mar 2020 09:30:40 -0300
2020-03-12 23:06:53
91.56.51.139 attack
2020-01-21T01:24:52.735Z CLOSE host=91.56.51.139 port=44574 fd=4 time=20.020 bytes=16
...
2020-03-12 23:10:40
123.205.106.88 attackbots
Unauthorized connection attempt from IP address 123.205.106.88 on Port 445(SMB)
2020-03-12 22:37:40
165.22.107.243 attackspam
165.22.107.243 - - \[12/Mar/2020:13:30:53 +0100\] "POST /wp-login.php HTTP/1.0" 200 7427 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
165.22.107.243 - - \[12/Mar/2020:13:30:55 +0100\] "POST /wp-login.php HTTP/1.0" 200 7242 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
165.22.107.243 - - \[12/Mar/2020:13:30:58 +0100\] "POST /wp-login.php HTTP/1.0" 200 7239 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2020-03-12 22:24:40
106.12.155.162 attackspam
Invalid user xvwei from 106.12.155.162 port 60264
2020-03-12 22:33:50
91.185.6.94 attackbots
2019-12-25T19:45:10.701Z CLOSE host=91.185.6.94 port=58760 fd=4 time=1050.506 bytes=1851
...
2020-03-12 23:15:23
183.87.76.57 attackbots
$f2bV_matches
2020-03-12 22:41:05
92.24.12.199 attackbotsspam
2020-03-04T17:25:42.553Z CLOSE host=92.24.12.199 port=10923 fd=8 time=40.019 bytes=45
...
2020-03-12 22:54:32
91.209.11.176 attack
2019-10-20T18:34:34.225Z CLOSE host=91.209.11.176 port=55885 fd=4 time=20.002 bytes=29
...
2020-03-12 23:13:42
95.142.172.150 attackspambots
2019-11-23T14:33:48.166Z CLOSE host=95.142.172.150 port=49721 fd=4 time=20.018 bytes=32
...
2020-03-12 22:43:02

Recently Reported IPs

56.152.225.191 242.200.106.234 147.170.207.97 136.92.195.15
27.188.110.8 81.61.24.38 12.37.116.248 19.96.181.180
87.71.126.158 176.246.49.164 200.32.179.18 188.180.101.114
205.245.93.18 236.110.92.13 69.252.72.228 215.241.60.102
197.207.157.230 104.19.244.203 127.57.32.110 234.225.228.29