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

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

;; QUESTION SECTION:
;25.4.50.142.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 03:57:48 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 142.50.4.25.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 142.50.4.25.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.155.74.38 attackspambots
Dec  1 10:00:15 ny01 sshd[29930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.74.38
Dec  1 10:00:18 ny01 sshd[29930]: Failed password for invalid user rpc from 139.155.74.38 port 42344 ssh2
Dec  1 10:05:05 ny01 sshd[30461]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.74.38
2019-12-01 23:19:43
41.37.168.71 attack
Port 1433 Scan
2019-12-01 23:48:36
134.175.111.215 attackspam
Dec  1 15:57:16 lnxded63 sshd[31018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.111.215
2019-12-01 23:32:56
172.116.84.144 attackspambots
port scan and connect, tcp 81 (hosts2-ns)
2019-12-01 23:42:11
104.129.41.145 attackbots
(From eric@talkwithcustomer.com) Hey,

You have a website mikulachiropractic.net, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a
2019-12-01 23:30:46
222.186.175.217 attackbotsspam
F2B jail: sshd. Time: 2019-12-01 16:32:38, Reported by: VKReport
2019-12-01 23:37:16
122.152.197.6 attackbots
$f2bV_matches
2019-12-02 00:03:57
159.203.201.135 attack
1575211507 - 12/01/2019 15:45:07 Host: 159.203.201.135/159.203.201.135 Port: 514 TCP Blocked
2019-12-01 23:49:27
129.213.122.26 attackspam
Dec  1 16:50:29 legacy sshd[586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26
Dec  1 16:50:30 legacy sshd[586]: Failed password for invalid user sanne from 129.213.122.26 port 44030 ssh2
Dec  1 16:53:43 legacy sshd[807]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26
...
2019-12-02 00:02:43
59.92.68.167 attackbotsspam
Unauthorized connection attempt from IP address 59.92.68.167 on Port 445(SMB)
2019-12-01 23:43:08
31.169.84.6 attack
Dec  1 11:34:41 ldap01vmsma01 sshd[64012]: Failed password for root from 31.169.84.6 port 56166 ssh2
...
2019-12-01 23:51:03
117.68.195.118 attackspambots
MAIL: User Login Brute Force Attempt
2019-12-01 23:41:20
41.38.166.172 attackspambots
SSH invalid-user multiple login try
2019-12-01 23:26:03
163.172.229.170 attackbotsspam
Dec  1 16:40:35 legacy sshd[32497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.229.170
Dec  1 16:40:37 legacy sshd[32497]: Failed password for invalid user lw from 163.172.229.170 port 42962 ssh2
Dec  1 16:43:31 legacy sshd[32718]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.229.170
...
2019-12-02 00:03:03
218.253.240.189 attack
[Sun Dec 01 11:45:35.736570 2019] [:error] [pid 127323] [client 218.253.240.189:48732] [client 218.253.240.189] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 18)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "127.0.0.1"] [uri "/cgi-bin/ViewLog.asp"] [unique_id "XePSD4vsLMOO7OL1RyZmLQAAAAI"]
...
2019-12-01 23:18:24

Recently Reported IPs

46.37.163.246 57.186.58.16 231.236.85.160 107.199.53.225
160.137.34.76 126.24.194.53 116.225.207.232 149.97.208.125
194.29.69.110 211.20.213.78 129.162.129.136 41.86.7.140
185.54.207.67 134.67.225.16 216.254.32.19 114.218.149.186
67.34.252.91 138.34.246.98 131.152.24.91 116.9.119.5