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: Williams Lake

Region: British Columbia

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

;; QUESTION SECTION:
;142.29.81.100.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 05 19:40:20 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 100.81.29.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 100.81.29.142.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
105.247.148.210 attack
postfix
2020-04-18 18:37:00
111.21.99.227 attackbotsspam
Apr 18 10:53:58 v22019038103785759 sshd\[6197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.21.99.227  user=root
Apr 18 10:54:00 v22019038103785759 sshd\[6197\]: Failed password for root from 111.21.99.227 port 36172 ssh2
Apr 18 11:03:06 v22019038103785759 sshd\[6793\]: Invalid user wd from 111.21.99.227 port 39792
Apr 18 11:03:06 v22019038103785759 sshd\[6793\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.21.99.227
Apr 18 11:03:08 v22019038103785759 sshd\[6793\]: Failed password for invalid user wd from 111.21.99.227 port 39792 ssh2
...
2020-04-18 18:50:11
23.108.47.56 attack
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across medenchiropractic.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www
2020-04-18 18:44:30
160.153.234.236 attackspambots
Apr 18 12:51:50 host sshd[12517]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-160-153-234-236.ip.secureserver.net  user=root
Apr 18 12:51:52 host sshd[12517]: Failed password for root from 160.153.234.236 port 41288 ssh2
...
2020-04-18 18:53:33
106.13.135.76 attackbots
2020-04-17 UTC: (16x) - css,docker,ds,ef,ey,git(2x),hd,m,rj,root(2x),test,test1,ubuntu,wf
2020-04-18 18:36:24
115.230.13.41 attackspambots
Apr 18 15:35:38 our-server-hostname postfix/smtpd[21684]: connect from unknown[115.230.13.41]
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x
Apr x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=115.230.13.41
2020-04-18 18:26:44
193.112.108.135 attackbots
$f2bV_matches
2020-04-18 18:31:16
162.213.253.61 attackspam
xmlrpc attack
2020-04-18 18:51:26
134.122.69.200 attackbotsspam
Apr 18 09:55:14 IngegnereFirenze sshd[6619]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.69.200  user=root
...
2020-04-18 18:17:45
112.26.98.122 attack
$f2bV_matches
2020-04-18 18:16:20
117.34.105.42 attack
Target: MSSQL :1433 [Brute-force]
2020-04-18 18:21:54
139.198.188.147 attackspam
Apr 18 08:10:06 h2646465 sshd[30855]: Invalid user vn from 139.198.188.147
Apr 18 08:10:06 h2646465 sshd[30855]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.188.147
Apr 18 08:10:06 h2646465 sshd[30855]: Invalid user vn from 139.198.188.147
Apr 18 08:10:08 h2646465 sshd[30855]: Failed password for invalid user vn from 139.198.188.147 port 48530 ssh2
Apr 18 08:20:57 h2646465 sshd[32605]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.188.147  user=root
Apr 18 08:20:59 h2646465 sshd[32605]: Failed password for root from 139.198.188.147 port 46086 ssh2
Apr 18 08:25:23 h2646465 sshd[760]: Invalid user pv from 139.198.188.147
Apr 18 08:25:23 h2646465 sshd[760]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.188.147
Apr 18 08:25:23 h2646465 sshd[760]: Invalid user pv from 139.198.188.147
Apr 18 08:25:25 h2646465 sshd[760]: Failed password for invalid user pv from 139.1
2020-04-18 18:20:42
123.206.255.17 attack
$f2bV_matches
2020-04-18 18:40:48
103.52.216.40 attackspam
Unauthorized connection attempt detected from IP address 103.52.216.40 to port 2048
2020-04-18 18:37:35
31.16.60.22 attackspambots
Unauthorized connection attempt detected from IP address 31.16.60.22 to port 23
2020-04-18 18:52:09

Recently Reported IPs

248.181.79.122 206.228.226.92 188.162.187.16 236.98.151.151
92.231.186.70 193.193.6.157 149.206.230.104 69.251.28.48
82.184.227.52 57.103.20.70 174.223.110.125 144.176.180.57
161.145.179.127 58.216.33.73 184.219.34.133 135.2.69.120
244.173.12.8 200.158.62.106 208.144.52.237 182.214.238.22