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

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

;; QUESTION SECTION:
;148.118.42.181.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 31 13:15:55 CST 2025
;; MSG SIZE  rcvd: 107
Host info
181.42.118.148.in-addr.arpa domain name pointer 181.42.118.148.in-addr.arpa.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
181.42.118.148.in-addr.arpa	name = 181.42.118.148.in-addr.arpa.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
114.67.229.131 attackbotsspam
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-07-16 14:28:14
104.236.214.8 attack
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-07-16 14:00:27
124.81.94.66 attackbots
*Port Scan* detected from 124.81.94.66 (ID/Indonesia/Jakarta/Jakarta/-). 4 hits in the last 235 seconds
2020-07-16 14:05:09
145.239.7.78 attack
20 attempts against mh_ha-misbehave-ban on flare
2020-07-16 14:19:55
23.90.28.66 attack
(From syme.chara@googlemail.com) Hi,

Do you have a Website? Of course you do because I am looking at your website martychiropractic.net now.

Are you struggling for Leads and Sales?

You’re not the only one.

So many Website owners struggle to convert their Visitors into Leads & Sales.

There’s a simple way to fix this problem.

You could use a Live Chat app on your Website martychiropractic.net and hire Chat Agents.

But only if you’ve got deep pockets and you’re happy to fork out THOUSANDS of dollars for the quality you need.

=====

But what if you could automate Live Chat so it’s HUMAN-FREE?

What if you could exploit NEW “AI” Technology to engage with your Visitors INSTANTLY.

And AUTOMATICALLY convert them into Leads & Sales.

WITHOUT spending THOUSANDS of dollars on Live Chat Agents.

And WITHOUT hiring expensive coders.

In fact, all you need to do to activate this LATEST “AI” Website Tech..

..is to COPY & PASTE a single line of “Website Code”.

==> http://www.zoomsof
2020-07-16 14:24:24
62.234.110.91 attack
Invalid user new from 62.234.110.91 port 34622
2020-07-16 14:28:55
40.68.202.110 attackbotsspam
failed root login
2020-07-16 14:27:17
193.56.28.108 attackspam
2020-07-16 08:02:50 auth_plain authenticator failed for (User) [193.56.28.108]: 535 Incorrect authentication data (set_id=web@com.ua,)
2020-07-16 08:02:50 auth_plain authenticator failed for (User) [193.56.28.108]: 535 Incorrect authentication data (set_id=web@com.ua,)
...
2020-07-16 14:17:59
125.141.139.9 attackbots
Jul 16 07:53:17 buvik sshd[2420]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.141.139.9
Jul 16 07:53:19 buvik sshd[2420]: Failed password for invalid user wjw from 125.141.139.9 port 60476 ssh2
Jul 16 07:58:07 buvik sshd[3115]: Invalid user sysadmin from 125.141.139.9
...
2020-07-16 14:26:22
95.178.156.60 attackbots
Telnetd brute force attack detected by fail2ban
2020-07-16 14:33:02
203.172.76.4 attackbots
Invalid user test from 203.172.76.4 port 58972
2020-07-16 14:38:23
61.174.60.170 attack
Jul 16 05:51:53 ns37 sshd[26825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.174.60.170
Jul 16 05:51:54 ns37 sshd[26825]: Failed password for invalid user sangeeta from 61.174.60.170 port 58498 ssh2
Jul 16 05:54:06 ns37 sshd[26922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.174.60.170
2020-07-16 14:01:33
218.92.0.251 attackspambots
Jul 16 08:27:31 santamaria sshd\[2216\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.251  user=root
Jul 16 08:27:33 santamaria sshd\[2216\]: Failed password for root from 218.92.0.251 port 34440 ssh2
Jul 16 08:27:50 santamaria sshd\[2218\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.251  user=root
...
2020-07-16 14:36:43
112.85.42.188 attackspambots
2020-07-16T09:13:25.748282lavrinenko.info sshd[4833]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.188  user=root
2020-07-16T09:13:27.599928lavrinenko.info sshd[4833]: Failed password for root from 112.85.42.188 port 21148 ssh2
2020-07-16T09:13:25.748282lavrinenko.info sshd[4833]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.188  user=root
2020-07-16T09:13:27.599928lavrinenko.info sshd[4833]: Failed password for root from 112.85.42.188 port 21148 ssh2
2020-07-16T09:13:30.295476lavrinenko.info sshd[4833]: Failed password for root from 112.85.42.188 port 21148 ssh2
...
2020-07-16 14:28:34
80.245.164.164 attackbotsspam
Port Scan detected!
...
2020-07-16 14:17:07

Recently Reported IPs

168.48.110.111 216.204.160.213 209.48.142.133 213.104.119.28
203.17.104.32 136.186.250.97 198.217.138.46 233.28.60.52
127.15.203.114 219.205.51.163 125.130.215.3 189.86.148.102
197.8.72.53 53.142.96.118 188.68.17.67 141.168.117.189
239.221.77.25 157.4.200.177 65.40.65.76 64.55.185.89