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: United States of America (the)

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

;; QUESTION SECTION:
;70.109.49.64.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 02 02:07:23 CST 2025
;; MSG SIZE  rcvd: 105
Host info
64.49.109.70.in-addr.arpa domain name pointer pool-70-109-49-64.clppva.fios.verizon.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
64.49.109.70.in-addr.arpa	name = pool-70-109-49-64.clppva.fios.verizon.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.8.167.27 attack
2020-08-31 07:22:10 login_virtual_exim authenticator failed for (In9EMuTfU) [106.8.167.27]: 535 Incorrect authentication data (set_id=strueber.stellpflug)


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=106.8.167.27
2020-09-07 00:26:18
134.202.64.131 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found staytunedchiropractic.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 softwa
2020-09-06 23:49:07
117.221.22.178 attackbots
20/9/5@13:56:03: FAIL: Alarm-Network address from=117.221.22.178
...
2020-09-07 00:30:31
176.62.108.211 attackspam
SMB Server BruteForce Attack
2020-09-07 00:21:01
201.95.86.224 attackbotsspam
Icarus honeypot on github
2020-09-07 00:06:05
223.235.185.241 attack
2020-09-05 11:36:29.170007-0500  localhost smtpd[41784]: NOQUEUE: reject: RCPT from unknown[223.235.185.241]: 554 5.7.1 Service unavailable; Client host [223.235.185.241] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/223.235.185.241; from= to= proto=ESMTP helo=<[223.235.185.241]>
2020-09-07 00:15:52
77.40.3.156 attackspambots
(smtpauth) Failed SMTP AUTH login from 77.40.3.156 (RU/Russia/156.3.dialup.mari-el.ru): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-09-06 19:30:39 plain authenticator failed for (localhost) [77.40.3.156]: 535 Incorrect authentication data (set_id=sales@yas-co.com)
2020-09-07 00:18:31
117.102.76.182 attack
Sep  5 18:48:36 ns381471 sshd[3761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.102.76.182
Sep  5 18:48:38 ns381471 sshd[3761]: Failed password for invalid user ubuntu from 117.102.76.182 port 37034 ssh2
2020-09-06 23:53:55
62.234.78.62 attack
...
2020-09-07 00:07:34
103.131.71.127 attack
(mod_security) mod_security (id:210730) triggered by 103.131.71.127 (VN/Vietnam/bot-103-131-71-127.coccoc.com): 5 in the last 3600 secs
2020-09-07 00:26:45
192.241.227.114 attack
TCP ports : 771 / 1723 / 1911
2020-09-07 00:16:48
141.85.216.231 attack
141.85.216.231 - - [06/Sep/2020:16:30:52 +0200] "POST /wp-login.php HTTP/1.0" 200 4793 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-09-06 23:54:11
154.119.7.3 attackspambots
 TCP (SYN) 154.119.7.3:56114 -> port 445, len 44
2020-09-06 23:53:07
90.151.180.215 attackspam
Dovecot Invalid User Login Attempt.
2020-09-06 23:58:28
109.70.100.49 attackspambots
Unauthorized connection attempt detected, IP banned.
2020-09-07 00:31:06

Recently Reported IPs

209.35.79.198 50.228.204.233 241.195.74.41 156.217.250.139
158.214.17.130 49.167.97.93 17.152.89.30 241.171.148.44
172.156.79.164 238.199.152.134 95.109.241.176 148.82.12.227
246.48.106.89 51.118.12.223 112.161.129.16 177.74.67.253
18.255.51.142 73.96.56.255 147.45.153.200 68.13.114.89