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

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

;; QUESTION SECTION:
;2.85.108.140.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 20:46:26 CST 2025
;; MSG SIZE  rcvd: 105
Host info
140.108.85.2.in-addr.arpa domain name pointer ppp-2-85-108-140.home.otenet.gr.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.108.85.2.in-addr.arpa	name = ppp-2-85-108-140.home.otenet.gr.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
221.149.134.160 attack
Jul 23 10:56:38 mxgate1 postfix/postscreen[17275]: CONNECT from [221.149.134.160]:30574 to [176.31.12.44]:25
Jul 23 10:56:38 mxgate1 postfix/dnsblog[17554]: addr 221.149.134.160 listed by domain cbl.abuseat.org as 127.0.0.2
Jul 23 10:56:38 mxgate1 postfix/dnsblog[17553]: addr 221.149.134.160 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 23 10:56:38 mxgate1 postfix/dnsblog[17553]: addr 221.149.134.160 listed by domain zen.spamhaus.org as 127.0.0.3
Jul 23 10:56:38 mxgate1 postfix/dnsblog[17550]: addr 221.149.134.160 listed by domain bl.spamcop.net as 127.0.0.2
Jul 23 10:56:38 mxgate1 postfix/dnsblog[17551]: addr 221.149.134.160 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul 23 10:56:38 mxgate1 postfix/dnsblog[17552]: addr 221.149.134.160 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 23 10:56:44 mxgate1 postfix/postscreen[17275]: DNSBL rank 6 for [221.149.134.160]:30574
Jul x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=221.149.134.1
2019-07-24 01:34:57
217.156.250.236 attack
ICMP MP Probe, Scan -
2019-07-24 01:55:15
174.138.40.132 attackbots
SSH Bruteforce Attack
2019-07-24 02:14:57
92.53.65.82 attack
Multiport scan : 7 ports scanned 3704 3763 3889 3976 3993 4114 4132
2019-07-24 02:22:57
23.245.143.84 attackspambots
(From eric@talkwithcustomer.com) Hello pomeroychiropractic.com,

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 pomeroychiropractic.com.
- 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 pomeroychiropractic.com, 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 –
2019-07-24 01:41:28
123.231.61.180 attackspam
Jul 23 14:28:25 mail sshd\[29531\]: Failed password for invalid user tuser from 123.231.61.180 port 34453 ssh2
Jul 23 14:46:07 mail sshd\[29824\]: Invalid user ross from 123.231.61.180 port 17680
...
2019-07-24 01:42:04
5.77.39.20 attackbotsspam
Jul 23 10:11:02 mercury wordpress(lukegirvin.co.uk)[29835]: XML-RPC authentication failure for luke from 5.77.39.20
...
2019-07-24 01:46:30
128.199.187.219 attack
Sql/code injection probe
2019-07-24 01:51:22
115.236.100.114 attackspam
Jul 23 11:11:02 nextcloud sshd\[16485\]: Invalid user test from 115.236.100.114
Jul 23 11:11:02 nextcloud sshd\[16485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.236.100.114
Jul 23 11:11:04 nextcloud sshd\[16485\]: Failed password for invalid user test from 115.236.100.114 port 65047 ssh2
...
2019-07-24 01:45:29
103.217.217.146 attack
2019-07-23T18:07:52.332469abusebot-8.cloudsearch.cf sshd\[1204\]: Invalid user shan from 103.217.217.146 port 50960
2019-07-24 02:10:23
175.101.137.244 attackbotsspam
60001/tcp 60001/tcp
[2019-06-25/07-23]2pkt
2019-07-24 02:12:39
139.59.34.17 attack
Jul 23 16:41:12 XXX sshd[19798]: Invalid user houx from 139.59.34.17 port 51250
2019-07-24 01:44:56
46.101.204.20 attack
Jul 23 17:58:31 yabzik sshd[29880]: Failed password for root from 46.101.204.20 port 45990 ssh2
Jul 23 18:03:00 yabzik sshd[31407]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.204.20
Jul 23 18:03:01 yabzik sshd[31407]: Failed password for invalid user uniform from 46.101.204.20 port 41646 ssh2
2019-07-24 01:55:40
69.94.140.116 attackspam
Lines containing failures of 69.94.140.116


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=69.94.140.116
2019-07-24 01:29:56
104.148.4.226 attackspambots
firewall-block, port(s): 445/tcp
2019-07-24 02:21:48

Recently Reported IPs

7.182.25.14 57.84.242.48 69.105.246.46 92.146.75.128
175.231.132.22 27.68.220.230 103.173.137.238 24.162.73.231
88.124.115.87 204.33.59.133 241.107.212.54 252.164.201.100
197.139.200.135 23.120.137.252 157.70.105.164 92.223.23.48
121.185.77.85 61.138.170.87 159.182.117.245 126.28.167.18