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

Region: Seoul

Country: South Korea

Internet Service Provider: unknown

Hostname: unknown

Organization: Korea Telecom

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

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

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

;; Query time: 1 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Mon Apr 15 17:26:32 +08 2019
;; MSG SIZE  rcvd: 118

Host info
Host 70.212.135.121.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

** server can't find 70.212.135.121.in-addr.arpa: NXDOMAIN

Related IP info:
Related comments:
IP Type Details Datetime
51.68.229.177 attack
php WP PHPmyadamin ABUSE blocked for 12h
2020-08-11 04:26:32
91.134.167.236 attack
Aug 10 15:36:44 web8 sshd\[26515\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.167.236  user=root
Aug 10 15:36:46 web8 sshd\[26515\]: Failed password for root from 91.134.167.236 port 10908 ssh2
Aug 10 15:42:05 web8 sshd\[29068\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.167.236  user=root
Aug 10 15:42:07 web8 sshd\[29068\]: Failed password for root from 91.134.167.236 port 51268 ssh2
Aug 10 15:45:52 web8 sshd\[31735\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.167.236  user=root
2020-08-11 04:14:38
46.246.65.170 attackbots
Auto report Web spam and bad bot from Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 | HTTP/1.1 | GET | Monday, August 10th 2020 @ 12:00:47
2020-08-11 04:04:45
2.177.198.202 attack
Unauthorized connection attempt from IP address 2.177.198.202 on Port 445(SMB)
2020-08-11 03:54:37
176.40.228.213 attack
Unauthorized connection attempt from IP address 176.40.228.213 on Port 445(SMB)
2020-08-11 04:05:30
107.175.158.44 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found palmerchiroga.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 that
2020-08-11 03:50:51
192.99.210.162 attack
SSH brute-force attempt
2020-08-11 04:05:03
49.233.14.115 attack
Aug 10 05:12:54 vm0 sshd[27629]: Failed password for root from 49.233.14.115 port 33286 ssh2
Aug 10 14:31:18 vm0 sshd[13190]: Failed password for root from 49.233.14.115 port 33204 ssh2
...
2020-08-11 04:07:21
51.89.115.64 attack
" "
2020-08-11 04:09:37
49.146.36.135 attack
Unauthorized connection attempt from IP address 49.146.36.135 on Port 445(SMB)
2020-08-11 03:54:04
141.98.10.200 attackspambots
2020-08-10T19:37:35.520570abusebot-5.cloudsearch.cf sshd[16038]: Invalid user admin from 141.98.10.200 port 36147
2020-08-10T19:37:35.527261abusebot-5.cloudsearch.cf sshd[16038]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.200
2020-08-10T19:37:35.520570abusebot-5.cloudsearch.cf sshd[16038]: Invalid user admin from 141.98.10.200 port 36147
2020-08-10T19:37:38.312339abusebot-5.cloudsearch.cf sshd[16038]: Failed password for invalid user admin from 141.98.10.200 port 36147 ssh2
2020-08-10T19:38:12.586369abusebot-5.cloudsearch.cf sshd[16108]: Invalid user admin from 141.98.10.200 port 39807
2020-08-10T19:38:12.591780abusebot-5.cloudsearch.cf sshd[16108]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.200
2020-08-10T19:38:12.586369abusebot-5.cloudsearch.cf sshd[16108]: Invalid user admin from 141.98.10.200 port 39807
2020-08-10T19:38:14.789752abusebot-5.cloudsearch.cf sshd[16108]: Failed
...
2020-08-11 03:50:20
192.99.34.142 attack
CF RAY ID: 5c0a27bc8e89ece6 IP Class: noRecord URI: /wp-login.php
2020-08-11 04:08:30
116.96.171.224 attackspambots
Unauthorized connection attempt from IP address 116.96.171.224 on Port 445(SMB)
2020-08-11 04:19:26
42.116.159.241 attack
Unauthorized connection attempt from IP address 42.116.159.241 on Port 445(SMB)
2020-08-11 04:26:52
141.98.81.176 attackspambots
Automated SQL Injection Attempt
2020-08-11 03:58:33

Recently Reported IPs

5.233.64.73 159.203.7.65 120.50.252.140 177.94.53.237
185.149.233.73 98.143.67.212 36.73.133.111 78.36.19.112
171.236.106.26 49.204.92.246 190.185.113.42 106.12.36.42
154.65.92.59 14.161.17.118 125.41.1.100 36.72.216.200
118.69.182.69 103.255.6.66 60.249.23.235 223.181.232.132