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

Region: Ar Riyad

Country: Saudi Arabia

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

;; QUESTION SECTION:
;134.239.191.70.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 08:16:13 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 70.191.239.134.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.191.239.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
142.93.52.3 attack
Apr 22 17:04:44 gw1 sshd[29988]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.52.3
Apr 22 17:04:46 gw1 sshd[29988]: Failed password for invalid user admin from 142.93.52.3 port 58626 ssh2
...
2020-04-22 20:39:37
106.12.209.117 attack
Apr 22 15:20:41 hosting sshd[11224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.117  user=root
Apr 22 15:20:43 hosting sshd[11224]: Failed password for root from 106.12.209.117 port 47710 ssh2
Apr 22 15:28:59 hosting sshd[11886]: Invalid user test from 106.12.209.117 port 58680
...
2020-04-22 21:06:20
222.186.42.155 attackspam
Apr 22 14:06:27 cat5e sshd[21426]: Failed password for root from 222.186.42.155 port 53629 ssh2
2020-04-22 21:14:24
118.33.213.3 attackspambots
Honeypot attack, port: 5555, PTR: PTR record not found
2020-04-22 21:16:33
172.245.193.245 attackbots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found millenniumchiro.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-04-22 20:46:06
109.75.44.224 attack
Unauthorised access (Apr 22) SRC=109.75.44.224 LEN=48 TTL=119 ID=19427 DF TCP DPT=445 WINDOW=8192 SYN
2020-04-22 20:55:30
150.136.67.237 attack
SSH auth scanning - multiple failed logins
2020-04-22 20:43:17
64.225.106.133 attack
(sshd) Failed SSH login from 64.225.106.133 (DE/Germany/-): 5 in the last 3600 secs
2020-04-22 21:22:56
191.102.156.130 attackbots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found millenniumchiro.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-04-22 20:42:48
222.186.30.76 attackbots
2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:43.907630sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:43.907630sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2
2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186
...
2020-04-22 20:57:38
94.102.56.181 attackspam
firewall-block, port(s): 9609/tcp
2020-04-22 21:22:25
95.213.187.236 attack
04/22/2020-08:13:41.175735 95.213.187.236 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-22 21:20:24
111.206.198.92 attackbots
Bad bot/spoofed identity
2020-04-22 21:00:10
178.128.108.100 attackspambots
Apr 22 18:59:42 itv-usvr-02 sshd[2295]: Invalid user tester from 178.128.108.100 port 41026
Apr 22 18:59:42 itv-usvr-02 sshd[2295]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.108.100
Apr 22 18:59:42 itv-usvr-02 sshd[2295]: Invalid user tester from 178.128.108.100 port 41026
Apr 22 18:59:44 itv-usvr-02 sshd[2295]: Failed password for invalid user tester from 178.128.108.100 port 41026 ssh2
Apr 22 19:04:04 itv-usvr-02 sshd[2409]: Invalid user lm from 178.128.108.100 port 42622
2020-04-22 21:17:42
176.31.93.62 attack
Apr 22 13:37:05 mail01 postfix/postscreen[28305]: CONNECT from [176.31.93.62]:33914 to [94.130.181.95]:25
Apr 22 13:37:05 mail01 postfix/dnsblog[28306]: addr 176.31.93.62 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Apr 22 13:37:11 mail01 postfix/postscreen[28305]: PASS NEW [176.31.93.62]:33914
Apr 22 13:37:12 mail01 postfix/smtpd[28308]: connect from de.infolawsuhostname.com[176.31.93.62]
Apr x@x
Apr 22 13:37:12 mail01 postfix/smtpd[28308]: disconnect from de.infolawsuhostname.com[176.31.93.62] ehlo=2 starttls=1 mail=1 rcpt=0/1 quhostname=1 commands=5/6
Apr 22 13:42:05 mail01 postfix/postscreen[28305]: CONNECT from [176.31.93.62]:40401 to [94.130.181.95]:25
Apr 22 13:42:05 mail01 postfix/dnsblog[28307]: addr 176.31.93.62 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Apr 22 13:42:05 mail01 postfix/postscreen[28305]: PASS OLD [176.31.93.62]:40401
Apr 22 13:42:05 mail01 postfix/smtpd[28308]: connect from de.infolawsuhostname.com[176.31.93.62]
Apr x@x
Apr 22 13:42........
-------------------------------
2020-04-22 21:15:39

Recently Reported IPs

16.135.114.88 48.113.200.76 238.205.119.113 255.255.168.192
38.71.235.220 65.166.10.213 230.219.225.81 99.198.7.39
107.246.10.99 27.137.242.104 142.25.235.192 127.168.186.68
186.101.16.170 148.188.4.104 152.172.152.76 217.234.125.190
160.147.184.68 225.144.143.158 166.17.143.91 246.41.159.241