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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;241.128.212.70.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 08:53:31 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 70.212.128.241.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 70.212.128.241.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
23.108.46.43 attackspam
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found drmichaeltwalsh.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 tha
2020-09-07 15:15:45
196.206.254.241 attackbots
Sep  7 04:32:53 scw-focused-cartwright sshd[17333]: Failed password for root from 196.206.254.241 port 56236 ssh2
Sep  7 04:47:14 scw-focused-cartwright sshd[17538]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.206.254.241
2020-09-07 15:47:14
192.3.15.162 attackbotsspam
Sep  7 07:21:13 markkoudstaal sshd[15037]: Failed password for root from 192.3.15.162 port 48076 ssh2
Sep  7 07:21:22 markkoudstaal sshd[15083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.15.162
Sep  7 07:21:25 markkoudstaal sshd[15083]: Failed password for invalid user oracle from 192.3.15.162 port 54418 ssh2
...
2020-09-07 15:24:08
49.233.130.95 attackbotsspam
Sep  7 07:52:29 dhoomketu sshd[2930568]: Failed password for invalid user content from 49.233.130.95 port 49780 ssh2
Sep  7 07:56:19 dhoomketu sshd[2930603]: Invalid user admin from 49.233.130.95 port 47700
Sep  7 07:56:19 dhoomketu sshd[2930603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.130.95 
Sep  7 07:56:19 dhoomketu sshd[2930603]: Invalid user admin from 49.233.130.95 port 47700
Sep  7 07:56:21 dhoomketu sshd[2930603]: Failed password for invalid user admin from 49.233.130.95 port 47700 ssh2
...
2020-09-07 15:16:50
192.144.215.146 attack
Port scan denied
2020-09-07 15:54:52
167.248.133.26 attackbots
 TCP (SYN) 167.248.133.26:61089 -> port 88, len 44
2020-09-07 15:18:02
104.46.32.174 attackbotsspam
Unauthorised login to NAS
2020-09-07 16:02:18
114.33.57.215 attack
port scan and connect, tcp 23 (telnet)
2020-09-07 15:20:10
104.155.213.9 attack
Sep  7 10:01:35 root sshd[14929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.155.213.9 
...
2020-09-07 16:05:54
49.69.205.106 attackspam
Aug 31 16:20:07 nxxxxxxx sshd[13756]: refused connect from 49.69.205.106 (49=
.69.205.106)


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.69.205.106
2020-09-07 15:04:12
190.8.116.177 attackspambots
$f2bV_matches
2020-09-07 15:55:22
191.102.156.164 attackspam
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found ottochiropractic.net 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 th
2020-09-07 15:05:48
95.152.30.49 attack
Honeypot attack, port: 445, PTR: host-95-152-30-49.dsl.sura.ru.
2020-09-07 15:08:36
49.235.153.54 attackbots
(sshd) Failed SSH login from 49.235.153.54 (CN/China/-): 5 in the last 3600 secs
2020-09-07 15:10:42
176.12.23.26 attackbots
Telnet Honeypot -> Telnet Bruteforce / Login
2020-09-07 15:49:56

Recently Reported IPs

164.131.126.99 114.139.254.197 29.206.8.218 205.8.195.56
51.67.63.36 227.61.227.137 130.59.106.116 223.195.188.183
57.104.170.160 97.172.229.201 248.60.8.173 203.56.83.155
153.207.28.245 51.218.34.198 162.66.248.162 93.236.67.44
18.236.13.223 139.65.226.22 184.185.108.22 132.120.118.186