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

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

;; QUESTION SECTION:
;200.129.211.148.		IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 00:02:23 CST 2025
;; MSG SIZE  rcvd: 108
Host info
148.211.129.200.in-addr.arpa domain name pointer 200-129-211-148.ufms.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
148.211.129.200.in-addr.arpa	name = 200-129-211-148.ufms.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.180.130 attackbots
2020-08-28T21:45:10.578879shield sshd\[392\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130  user=root
2020-08-28T21:45:12.470240shield sshd\[392\]: Failed password for root from 222.186.180.130 port 54814 ssh2
2020-08-28T21:45:14.575304shield sshd\[392\]: Failed password for root from 222.186.180.130 port 54814 ssh2
2020-08-28T21:45:16.963742shield sshd\[392\]: Failed password for root from 222.186.180.130 port 54814 ssh2
2020-08-28T21:45:20.599034shield sshd\[468\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130  user=root
2020-08-29 05:52:40
181.189.144.206 attack
Invalid user sysbackup from 181.189.144.206 port 39488
2020-08-29 06:03:05
85.209.0.101 attack
Aug 23 03:12:49 : SSH login attempts with invalid user
2020-08-29 06:09:11
85.9.66.15 attackspambots
Aug 29 00:47:16 lukav-desktop sshd\[5301\]: Invalid user git from 85.9.66.15
Aug 29 00:47:16 lukav-desktop sshd\[5301\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.9.66.15
Aug 29 00:47:18 lukav-desktop sshd\[5301\]: Failed password for invalid user git from 85.9.66.15 port 32876 ssh2
Aug 29 00:48:03 lukav-desktop sshd\[5307\]: Invalid user vic from 85.9.66.15
Aug 29 00:48:03 lukav-desktop sshd\[5307\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.9.66.15
2020-08-29 06:06:37
201.192.152.202 attack
Aug 28 23:38:45 abendstille sshd\[14817\]: Invalid user readonly from 201.192.152.202
Aug 28 23:38:45 abendstille sshd\[14817\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.192.152.202
Aug 28 23:38:47 abendstille sshd\[14817\]: Failed password for invalid user readonly from 201.192.152.202 port 46628 ssh2
Aug 28 23:44:06 abendstille sshd\[20060\]: Invalid user admin from 201.192.152.202
Aug 28 23:44:06 abendstille sshd\[20060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.192.152.202
...
2020-08-29 05:44:57
195.54.161.252 attackbotsspam
Aug 24 02:27:46 : SSH login attempts with invalid user
2020-08-29 06:07:59
106.12.57.149 attack
Invalid user oracle from 106.12.57.149 port 60870
2020-08-29 06:18:00
209.141.61.233 attackspam
Fail2Ban Ban Triggered
2020-08-29 06:10:33
134.209.24.61 attack
Aug 28 17:55:47 ny01 sshd[13646]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.24.61
Aug 28 17:55:49 ny01 sshd[13646]: Failed password for invalid user john from 134.209.24.61 port 42184 ssh2
Aug 28 17:59:37 ny01 sshd[14258]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.24.61
2020-08-29 06:01:54
198.46.189.106 attack
SSH Brute-Force. Ports scanning.
2020-08-29 05:51:36
189.90.255.108 attackspam
Aug 28 23:51:50 vps647732 sshd[5046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.90.255.108
Aug 28 23:51:52 vps647732 sshd[5046]: Failed password for invalid user okamura from 189.90.255.108 port 50266 ssh2
...
2020-08-29 06:15:58
189.4.2.58 attackspambots
SSH Invalid Login
2020-08-29 05:52:07
119.29.119.151 attackbotsspam
SSH Invalid Login
2020-08-29 06:10:49
154.16.203.118 attackbots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found drjamieswellnesscenter.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new softw
2020-08-29 06:08:24
122.51.10.222 attackbots
$f2bV_matches
2020-08-29 05:42:55

Recently Reported IPs

131.236.28.11 126.232.147.2 141.252.59.137 170.210.140.173
56.195.124.74 136.5.47.159 234.151.224.126 245.155.198.127
154.196.122.241 244.7.202.176 134.223.218.18 56.196.91.25
232.204.192.237 186.239.136.249 80.232.116.51 42.170.169.67
221.202.224.251 97.212.111.235 127.158.31.191 42.33.208.110