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

Region: Oregon

Country: United States

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;44.229.199.2.			IN	A

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

;; Query time: 104 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 24 07:41:41 CST 2019
;; MSG SIZE  rcvd: 116
Host info
2.199.229.44.in-addr.arpa domain name pointer ec2-44-229-199-2.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.199.229.44.in-addr.arpa	name = ec2-44-229-199-2.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.120.126.246 attackbotsspam
20/2/26@08:37:23: FAIL: Alarm-Network address from=103.120.126.246
...
2020-02-26 23:20:20
45.152.32.21 attackbots
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - drbrianferris.info - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across drbrianferris.info, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

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 lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over you
2020-02-26 23:23:29
167.114.251.164 attackspambots
2020-02-26T16:12:39.935833  sshd[320]: Invalid user sys from 167.114.251.164 port 40437
2020-02-26T16:12:39.949066  sshd[320]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.251.164
2020-02-26T16:12:39.935833  sshd[320]: Invalid user sys from 167.114.251.164 port 40437
2020-02-26T16:12:41.432298  sshd[320]: Failed password for invalid user sys from 167.114.251.164 port 40437 ssh2
...
2020-02-26 23:41:36
212.81.180.201 attackbots
$f2bV_matches
2020-02-26 23:26:22
71.165.90.119 attack
Feb 26 19:09:27 gw1 sshd[25463]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.165.90.119
Feb 26 19:09:28 gw1 sshd[25463]: Failed password for invalid user ackerjapan from 71.165.90.119 port 33766 ssh2
...
2020-02-26 22:56:45
212.95.137.242 attackspam
$f2bV_matches
2020-02-26 23:21:55
190.202.54.12 attack
Feb 26 15:13:58 localhost sshd\[7636\]: Invalid user liangying from 190.202.54.12 port 23100
Feb 26 15:13:58 localhost sshd\[7636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.202.54.12
Feb 26 15:14:00 localhost sshd\[7636\]: Failed password for invalid user liangying from 190.202.54.12 port 23100 ssh2
Feb 26 15:19:04 localhost sshd\[7763\]: Invalid user tom from 190.202.54.12 port 41058
Feb 26 15:19:04 localhost sshd\[7763\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.202.54.12
...
2020-02-26 23:22:23
177.200.115.65 attackbots
1582724254 - 02/26/2020 14:37:34 Host: 177.200.115.65/177.200.115.65 Port: 445 TCP Blocked
2020-02-26 23:05:25
82.196.15.195 attackbots
$f2bV_matches
2020-02-26 23:22:41
106.13.40.177 attack
Invalid user daniel from 106.13.40.177 port 38838
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.40.177
Failed password for invalid user daniel from 106.13.40.177 port 38838 ssh2
Invalid user cpanelrrdtool from 106.13.40.177 port 47390
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.40.177
2020-02-26 23:25:46
212.68.208.120 attack
$f2bV_matches
2020-02-26 23:28:56
113.110.224.72 attackbotsspam
suspicious action Wed, 26 Feb 2020 10:37:30 -0300
2020-02-26 23:11:44
64.94.208.230 attackbotsspam
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - drbrianferris.info - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across drbrianferris.info, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

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 lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over you
2020-02-26 23:35:00
106.12.215.238 attackbots
(sshd) Failed SSH login from 106.12.215.238 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 26 15:52:51 amsweb01 sshd[18716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238  user=root
Feb 26 15:52:53 amsweb01 sshd[18716]: Failed password for root from 106.12.215.238 port 51792 ssh2
Feb 26 15:54:47 amsweb01 sshd[18878]: User mysql from 106.12.215.238 not allowed because not listed in AllowUsers
Feb 26 15:54:47 amsweb01 sshd[18878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238  user=mysql
Feb 26 15:54:48 amsweb01 sshd[18878]: Failed password for invalid user mysql from 106.12.215.238 port 39108 ssh2
2020-02-26 22:59:08
213.138.73.250 attackspam
$f2bV_matches
2020-02-26 23:19:05

Recently Reported IPs

103.6.196.43 188.81.163.55 186.206.144.144 94.142.139.229
32.243.156.73 110.250.9.165 194.147.35.219 103.59.213.2
173.97.72.236 41.107.156.227 117.131.60.38 126.149.198.88
91.134.116.166 177.19.5.101 91.240.86.223 74.222.4.14
185.84.6.103 3.180.56.186 158.69.70.163 150.136.133.20