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

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

;; QUESTION SECTION:
;85.7.42.103.			IN	A

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

;; Query time: 31 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 06:20:23 CST 2025
;; MSG SIZE  rcvd: 104
Host info
103.42.7.85.in-addr.arpa domain name pointer 103.42.7.85.dynamic.cust.swisscom.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
103.42.7.85.in-addr.arpa	name = 103.42.7.85.dynamic.cust.swisscom.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
122.128.107.61 attack
Invalid user dalling from 122.128.107.61 port 54448
2019-12-22 04:55:54
54.39.138.251 attackspam
Dec 21 11:01:24 kapalua sshd\[16557\]: Invalid user hcf from 54.39.138.251
Dec 21 11:01:24 kapalua sshd\[16557\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip251.ip-54-39-138.net
Dec 21 11:01:26 kapalua sshd\[16557\]: Failed password for invalid user hcf from 54.39.138.251 port 50612 ssh2
Dec 21 11:06:44 kapalua sshd\[17115\]: Invalid user franci from 54.39.138.251
Dec 21 11:06:44 kapalua sshd\[17115\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip251.ip-54-39-138.net
2019-12-22 05:10:50
114.67.84.230 attackbots
Dec 21 05:44:10 hpm sshd\[32572\]: Invalid user fs from 114.67.84.230
Dec 21 05:44:10 hpm sshd\[32572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.84.230
Dec 21 05:44:11 hpm sshd\[32572\]: Failed password for invalid user fs from 114.67.84.230 port 58404 ssh2
Dec 21 05:52:00 hpm sshd\[900\]: Invalid user bsamexico from 114.67.84.230
Dec 21 05:52:00 hpm sshd\[900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.84.230
2019-12-22 05:11:07
62.234.106.199 attackspam
$f2bV_matches
2019-12-22 04:47:33
185.253.96.27 attackbotsspam
0,41-00/00 [bc01/m10] PostRequest-Spammer scoring: zurich
2019-12-22 04:46:32
206.189.137.113 attackbots
Dec 21 21:24:28 icinga sshd[14067]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.137.113
Dec 21 21:24:29 icinga sshd[14067]: Failed password for invalid user admin from 206.189.137.113 port 40930 ssh2
...
2019-12-22 05:15:32
68.183.91.25 attackbotsspam
Dec 21 11:10:28 plusreed sshd[11577]: Invalid user ehrsam from 68.183.91.25
...
2019-12-22 04:58:40
49.233.136.245 attack
Dec 16 18:02:15 zimbra sshd[7950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.136.245  user=r.r
Dec 16 18:02:17 zimbra sshd[7950]: Failed password for r.r from 49.233.136.245 port 51236 ssh2
Dec 16 18:02:17 zimbra sshd[7950]: Received disconnect from 49.233.136.245 port 51236:11: Bye Bye [preauth]
Dec 16 18:02:17 zimbra sshd[7950]: Disconnected from 49.233.136.245 port 51236 [preauth]
Dec 16 18:13:56 zimbra sshd[17210]: Invalid user test from 49.233.136.245
Dec 16 18:13:56 zimbra sshd[17210]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.136.245
Dec 16 18:13:58 zimbra sshd[17210]: Failed password for invalid user test from 49.233.136.245 port 56854 ssh2
Dec 16 18:13:58 zimbra sshd[17210]: Received disconnect from 49.233.136.245 port 56854:11: Bye Bye [preauth]
Dec 16 18:13:58 zimbra sshd[17210]: Disconnected from 49.233.136.245 port 56854 [preauth]
Dec 16 18:20:10 zimbra........
-------------------------------
2019-12-22 04:42:27
187.44.162.156 attackspambots
Dec 21 20:15:45 IngegnereFirenze sshd[22057]: Failed password for invalid user ericf from 187.44.162.156 port 10249 ssh2
...
2019-12-22 05:14:02
175.211.59.177 attack
Dec 21 11:02:31 kapalua sshd\[16680\]: Invalid user eskeland from 175.211.59.177
Dec 21 11:02:31 kapalua sshd\[16680\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.211.59.177
Dec 21 11:02:32 kapalua sshd\[16680\]: Failed password for invalid user eskeland from 175.211.59.177 port 58012 ssh2
Dec 21 11:07:52 kapalua sshd\[17298\]: Invalid user musicbot from 175.211.59.177
Dec 21 11:07:52 kapalua sshd\[17298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.211.59.177
2019-12-22 05:09:44
58.56.33.221 attack
Dec 21 19:53:47 MainVPS sshd[27777]: Invalid user len from 58.56.33.221 port 52630
Dec 21 19:53:47 MainVPS sshd[27777]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.56.33.221
Dec 21 19:53:47 MainVPS sshd[27777]: Invalid user len from 58.56.33.221 port 52630
Dec 21 19:53:49 MainVPS sshd[27777]: Failed password for invalid user len from 58.56.33.221 port 52630 ssh2
Dec 21 19:58:27 MainVPS sshd[4204]: Invalid user svarverud from 58.56.33.221 port 47286
...
2019-12-22 04:43:27
198.245.63.94 attack
Dec 21 05:31:39 auw2 sshd\[22457\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns508619.ip-198-245-63.net  user=www-data
Dec 21 05:31:41 auw2 sshd\[22457\]: Failed password for www-data from 198.245.63.94 port 51358 ssh2
Dec 21 05:37:01 auw2 sshd\[22991\]: Invalid user phone from 198.245.63.94
Dec 21 05:37:01 auw2 sshd\[22991\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns508619.ip-198-245-63.net
Dec 21 05:37:03 auw2 sshd\[22991\]: Failed password for invalid user phone from 198.245.63.94 port 55956 ssh2
2019-12-22 05:11:33
185.40.20.70 attackbotsspam
Dec 16 16:44:51 ihdb003 sshd[28875]: Connection from 185.40.20.70 port 45654 on 178.128.173.140 port 22
Dec 16 16:44:51 ihdb003 sshd[28875]: Did not receive identification string from 185.40.20.70 port 45654
Dec 16 17:36:10 ihdb003 sshd[28996]: Connection from 185.40.20.70 port 43428 on 178.128.173.140 port 22
Dec 16 17:36:10 ihdb003 sshd[28996]: Did not receive identification string from 185.40.20.70 port 43428
Dec 16 17:37:14 ihdb003 sshd[28997]: Connection from 185.40.20.70 port 59456 on 178.128.173.140 port 22
Dec 16 17:37:14 ihdb003 sshd[28997]: Did not receive identification string from 185.40.20.70 port 59456
Dec 16 17:40:05 ihdb003 sshd[29012]: Connection from 185.40.20.70 port 57164 on 178.128.173.140 port 22
Dec 16 17:40:06 ihdb003 sshd[29012]: Invalid user ftpuser from 185.40.20.70 port 57164
Dec 16 17:40:06 ihdb003 sshd[29012]: Received disconnect from 185.40.20.70 port 57164:11: Normal Shutdown, Thank you for playing [preauth]
Dec 16 17:40:06 ihdb003 sshd[2........
-------------------------------
2019-12-22 04:43:52
107.174.149.177 attackspambots
(From eric@talkwithcustomer.com) Hello nwchiro.net,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website nwchiro.net.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website nwchiro.net, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famous marketer put it, “you
2019-12-22 05:16:27
193.56.28.159 attackbots
Dec 21 09:49:15 web1 postfix/smtpd[14861]: warning: unknown[193.56.28.159]: SASL LOGIN authentication failed: authentication failure
Dec 21 09:49:15 web1 postfix/smtpd[14861]: warning: unknown[193.56.28.159]: SASL LOGIN authentication failed: authentication failure
...
2019-12-22 05:03:48

Recently Reported IPs

148.73.112.127 156.169.226.142 214.209.89.239 20.88.26.25
50.12.240.250 58.27.186.214 63.69.41.220 164.9.149.161
108.45.37.8 104.246.54.131 210.125.147.107 80.184.19.167
179.231.144.129 13.45.205.35 247.143.4.5 245.127.26.147
30.51.119.110 8.32.227.253 43.207.62.22 46.253.12.83