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: Netherlands (the)

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

;; QUESTION SECTION:
;213.132.199.117.		IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 02:17:32 CST 2025
;; MSG SIZE  rcvd: 108
Host info
117.199.132.213.in-addr.arpa domain name pointer uyldert.nl.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
117.199.132.213.in-addr.arpa	name = uyldert.nl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
174.253.160.51 attacknormal
seriously
2020-04-16 07:06:05
150.109.113.230 attackspambots
Unauthorized connection attempt detected from IP address 150.109.113.230 to port 6379
2020-04-16 07:02:43
216.180.105.236 attack
(From lothian.winifred@hotmail.com) If you’ve been online any amount of time, you’re most likely still struggling to make the money you want online…

Am I right?

Well, we’re confident to say that you’ve come to the right place.

You might be thinking… Why are we different from the thousands of so-called “expert marketers” out there?

For one, I have the power to read your mind. I know exactly why you’re struggling right now...

OK - maybe reading your mind is a bit far fetched.

But what I can tell you is this…

We’ve worked with over 45,000+ customers.

And if they were struggling, we noticed it always came down to ONE important factor…

=>> http://bit.ly/UnlTraffic

You don't need to work for anyone else.

You don't need to take orders from your boss.

And you don't need to take permission to take vacation or spend a day with family.

And this is not just talk, let me show you real PROOF…

=>> http://bit.ly/UnlTraffic

Cheers
2020-04-16 07:31:27
181.123.9.3 attack
SSH Brute-Forcing (server1)
2020-04-16 07:18:06
64.225.12.205 attack
2020-04-15T23:11:58.096245dmca.cloudsearch.cf sshd[3722]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.12.205  user=root
2020-04-15T23:11:59.900770dmca.cloudsearch.cf sshd[3722]: Failed password for root from 64.225.12.205 port 46062 ssh2
2020-04-15T23:18:09.353432dmca.cloudsearch.cf sshd[4160]: Invalid user alex from 64.225.12.205 port 55638
2020-04-15T23:18:09.360362dmca.cloudsearch.cf sshd[4160]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.12.205
2020-04-15T23:18:09.353432dmca.cloudsearch.cf sshd[4160]: Invalid user alex from 64.225.12.205 port 55638
2020-04-15T23:18:11.766696dmca.cloudsearch.cf sshd[4160]: Failed password for invalid user alex from 64.225.12.205 port 55638 ssh2
2020-04-15T23:21:42.728447dmca.cloudsearch.cf sshd[4460]: Invalid user sys from 64.225.12.205 port 34088
...
2020-04-16 07:33:53
111.40.217.92 attackspam
DATE:2020-04-16 00:20:09, IP:111.40.217.92, PORT:ssh SSH brute force auth (docker-dc)
2020-04-16 07:15:22
106.12.182.1 attackspam
Invalid user guest from 106.12.182.1 port 37328
2020-04-16 07:19:25
177.23.184.99 attackspam
SSH Invalid Login
2020-04-16 07:33:25
110.80.17.26 attackspam
Apr 15 22:22:55 OPSO sshd\[29573\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.80.17.26  user=ftp
Apr 15 22:22:57 OPSO sshd\[29573\]: Failed password for ftp from 110.80.17.26 port 39994 ssh2
Apr 15 22:23:38 OPSO sshd\[29758\]: Invalid user vagrant from 110.80.17.26 port 45290
Apr 15 22:23:38 OPSO sshd\[29758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.80.17.26
Apr 15 22:23:40 OPSO sshd\[29758\]: Failed password for invalid user vagrant from 110.80.17.26 port 45290 ssh2
2020-04-16 07:08:22
138.197.66.68 attack
Apr 15 07:41:41: Invalid user mcUser from 138.197.66.68 port 60586
2020-04-16 07:21:57
177.76.75.31 attackspambots
Automatic report - Port Scan Attack
2020-04-16 07:20:44
65.97.0.208 attack
Invalid user serge from 65.97.0.208 port 33494
2020-04-16 07:22:28
89.106.108.253 attackspambots
scan z
2020-04-16 07:12:53
142.93.232.102 attackspambots
Invalid user zxin20 from 142.93.232.102 port 35544
2020-04-16 06:56:56
51.161.18.75 attack
Fail2Ban Ban Triggered
2020-04-16 07:11:27

Recently Reported IPs

255.231.39.27 18.35.197.220 250.27.22.137 227.144.99.152
103.82.23.223 246.20.138.4 23.168.170.227 90.202.254.115
226.97.201.38 66.249.65.88 51.211.40.227 64.75.189.21
241.240.143.178 207.142.0.106 140.120.76.209 70.157.160.104
64.143.106.102 132.176.247.148 55.181.164.31 58.98.56.190