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

Region: Pennsylvania

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: PenTeleData Inc.

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

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

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

;; Query time: 1 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Thu Sep 05 02:25:24 CST 2019
;; MSG SIZE  rcvd: 115
Host info
22.11.44.70.in-addr.arpa domain name pointer 70.44.11.22.res-cmts.flt3.ptd.net.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
22.11.44.70.in-addr.arpa	name = 70.44.11.22.res-cmts.flt3.ptd.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
182.43.225.34 attackbotsspam
2020-06-03T13:44[Censored Hostname] sshd[2312455]: Failed password for root from 182.43.225.34 port 57484 ssh2
2020-06-03T13:48[Censored Hostname] sshd[2312478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.43.225.34  user=root
2020-06-03T13:48[Censored Hostname] sshd[2312478]: Failed password for root from 182.43.225.34 port 57638 ssh2[...]
2020-06-04 02:47:49
192.144.172.50 attack
Jun  3 20:43:08 server sshd[11343]: Failed password for root from 192.144.172.50 port 52666 ssh2
Jun  3 20:47:10 server sshd[11683]: Failed password for root from 192.144.172.50 port 41942 ssh2
...
2020-06-04 02:58:04
106.12.209.57 attackbotsspam
Repeated brute force against a port
2020-06-04 03:17:04
195.161.162.46 attackbotsspam
DATE:2020-06-03 19:24:58, IP:195.161.162.46, PORT:ssh SSH brute force auth (docker-dc)
2020-06-04 03:19:22
199.119.144.20 attackbotsspam
SSH bruteforce
2020-06-04 02:57:49
79.185.195.84 attackspambots
Automatic report - Port Scan Attack
2020-06-04 02:44:49
91.151.93.33 attack
2020-06-03 06:41:03.676536-0500  localhost smtpd[89583]: NOQUEUE: reject: RCPT from unknown[91.151.93.33]: 450 4.7.25 Client host rejected: cannot find your hostname, [91.151.93.33]; from= to= proto=ESMTP helo=
2020-06-04 03:06:42
162.243.145.55 attack
Jun  3 21:28:46 debian kernel: [111490.529557] [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:be:e4:65:08:e8:4f:6e:48:0c:08:00 SRC=162.243.145.55 DST=89.252.131.35 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=54321 PROTO=TCP SPT=45898 DPT=9043 WINDOW=65535 RES=0x00 SYN URGP=0
2020-06-04 02:50:23
45.61.163.175 attack
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with advancedchirosolutions.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capt
2020-06-04 03:11:31
139.59.40.159 attack
xmlrpc attack
2020-06-04 02:45:02
180.166.141.58 attackbots
[H1.VM7] Blocked by UFW
2020-06-04 02:42:42
36.43.65.28 attackspambots
Port scan on 1 port(s): 23
2020-06-04 02:54:04
117.50.126.15 attackspam
Jun  3 14:34:43 eventyay sshd[17788]: Failed password for root from 117.50.126.15 port 22271 ssh2
Jun  3 14:38:31 eventyay sshd[17849]: Failed password for root from 117.50.126.15 port 3062 ssh2
...
2020-06-04 03:01:29
5.173.32.4 attackbotsspam
xmlrpc attack
2020-06-04 03:19:00
201.219.50.217 attackbots
Lines containing failures of 201.219.50.217
Jun  1 20:00:35 g sshd[7731]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.219.50.217  user=r.r
Jun  1 20:00:37 g sshd[7731]: Failed password for r.r from 201.219.50.217 port 57752 ssh2
Jun  1 20:00:37 g sshd[7731]: Received disconnect from 201.219.50.217 port 57752:11: Bye Bye [preauth]
Jun  1 20:00:37 g sshd[7731]: Disconnected from authenticating user r.r 201.219.50.217 port 57752 [preauth]
Jun  1 20:05:16 g sshd[7785]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.219.50.217  user=r.r
Jun  1 20:05:18 g sshd[7785]: Failed password for r.r from 201.219.50.217 port 44962 ssh2
Jun  1 20:05:18 g sshd[7785]: Received disconnect from 201.219.50.217 port 44962:11: Bye Bye [preauth]
Jun  1 20:05:18 g sshd[7785]: Disconnected from authenticating user r.r 201.219.50.217 port 44962 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.
2020-06-04 03:21:40

Recently Reported IPs

187.125.164.229 14.155.99.143 192.119.111.20 200.46.54.198
105.16.195.172 79.138.176.204 56.68.247.139 106.232.231.149
41.205.159.133 67.213.233.4 83.219.177.111 13.25.207.158
195.229.228.191 98.237.142.151 86.96.140.116 34.223.146.108
206.86.124.103 106.254.106.68 164.68.123.63 189.212.235.170