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

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

;; QUESTION SECTION:
;142.180.242.218.		IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 03:59:33 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 218.242.180.142.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 218.242.180.142.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
93.87.17.100 attack
" "
2020-03-12 02:09:23
23.245.154.67 attack
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found kestenchiro.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 software that ca
2020-03-12 02:24:55
163.44.168.207 attackbots
2020-03-11T04:40:56.236380linuxbox-skyline sshd[28249]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.44.168.207  user=root
2020-03-11T04:40:58.282144linuxbox-skyline sshd[28249]: Failed password for root from 163.44.168.207 port 48860 ssh2
...
2020-03-12 02:36:08
122.51.188.20 attackspambots
Fail2Ban - SSH Bruteforce Attempt
2020-03-12 02:19:50
95.213.143.90 attackbotsspam
Mar 11 14:09:53 ws19vmsma01 sshd[83240]: Failed password for root from 95.213.143.90 port 35896 ssh2
...
2020-03-12 02:05:48
123.20.123.107 attack
SSH login attempts.
2020-03-12 02:38:03
139.59.169.103 attackbots
Invalid user oracle from 139.59.169.103 port 50660
2020-03-12 02:09:49
213.32.23.58 attackbots
fail2ban
2020-03-12 02:02:21
107.170.63.221 attackspambots
2020-03-11T13:50:50.804932abusebot-3.cloudsearch.cf sshd[26439]: Invalid user alice from 107.170.63.221 port 36304
2020-03-11T13:50:50.811691abusebot-3.cloudsearch.cf sshd[26439]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.63.221
2020-03-11T13:50:50.804932abusebot-3.cloudsearch.cf sshd[26439]: Invalid user alice from 107.170.63.221 port 36304
2020-03-11T13:50:52.720184abusebot-3.cloudsearch.cf sshd[26439]: Failed password for invalid user alice from 107.170.63.221 port 36304 ssh2
2020-03-11T13:56:55.914538abusebot-3.cloudsearch.cf sshd[26942]: Invalid user paul from 107.170.63.221 port 52204
2020-03-11T13:56:55.920773abusebot-3.cloudsearch.cf sshd[26942]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.63.221
2020-03-11T13:56:55.914538abusebot-3.cloudsearch.cf sshd[26942]: Invalid user paul from 107.170.63.221 port 52204
2020-03-11T13:56:57.271942abusebot-3.cloudsearch.cf sshd[26942]: F
...
2020-03-12 02:17:39
189.243.29.60 attackbots
Invalid user web from 189.243.29.60 port 46508
2020-03-12 02:05:20
211.63.242.80 attack
Honeypot attack, port: 81, PTR: PTR record not found
2020-03-12 02:02:38
125.160.64.145 attackspambots
port scan and connect, tcp 22 (ssh)
2020-03-12 02:19:24
122.51.96.57 attackspam
2020-03-11T05:45:30.699186linuxbox-skyline sshd[29515]: Invalid user download from 122.51.96.57 port 54068
...
2020-03-12 02:33:19
51.75.254.172 attackbots
suspicious action Wed, 11 Mar 2020 15:31:21 -0300
2020-03-12 02:42:09
95.255.116.17 attackbotsspam
Honeypot attack, port: 81, PTR: host-95-255-116-17.business.telecomitalia.it.
2020-03-12 02:32:27

Recently Reported IPs

246.184.96.216 40.78.71.254 196.151.161.215 240.225.223.107
96.186.248.20 15.128.102.236 94.233.72.134 6.70.70.49
133.108.155.104 55.3.158.110 152.189.79.184 99.18.190.73
129.91.45.230 95.167.85.81 124.213.36.110 17.185.242.186
197.30.79.166 47.223.126.123 100.40.45.122 121.24.162.2