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

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

;; QUESTION SECTION:
;30.212.207.242.			IN	A

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

;; Query time: 327 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 09 08:29:43 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 242.207.212.30.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 242.207.212.30.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.83.75.97 attack
2020-04-15T21:39:13.270543shield sshd\[4364\]: Invalid user test from 51.83.75.97 port 39946
2020-04-15T21:39:13.274452shield sshd\[4364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=97.ip-51-83-75.eu
2020-04-15T21:39:14.776104shield sshd\[4364\]: Failed password for invalid user test from 51.83.75.97 port 39946 ssh2
2020-04-15T21:41:09.325360shield sshd\[4755\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=97.ip-51-83-75.eu  user=root
2020-04-15T21:41:11.419363shield sshd\[4755\]: Failed password for root from 51.83.75.97 port 46326 ssh2
2020-04-16 07:38:17
123.184.42.217 attackbots
Apr 16 04:28:39 webhost01 sshd[19045]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.184.42.217
Apr 16 04:28:40 webhost01 sshd[19045]: Failed password for invalid user wt from 123.184.42.217 port 54208 ssh2
...
2020-04-16 07:23:38
59.173.12.106 attackspambots
failed_logins
2020-04-16 07:10:41
177.76.75.31 attackspambots
Automatic report - Port Scan Attack
2020-04-16 07:20:44
49.234.16.16 attackspam
04/15/2020-16:56:02.342541 49.234.16.16 Protocol: 6 ET SCAN Potential SSH Scan
2020-04-16 07:20:19
106.12.56.143 attackbotsspam
SSH Invalid Login
2020-04-16 07:44:51
68.183.124.53 attack
2020-04-16T00:31:37.486480ns386461 sshd\[5209\]: Invalid user admin from 68.183.124.53 port 52222
2020-04-16T00:31:37.491317ns386461 sshd\[5209\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.124.53
2020-04-16T00:31:39.270438ns386461 sshd\[5209\]: Failed password for invalid user admin from 68.183.124.53 port 52222 ssh2
2020-04-16T00:41:53.968189ns386461 sshd\[14235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.124.53  user=root
2020-04-16T00:41:56.314407ns386461 sshd\[14235\]: Failed password for root from 68.183.124.53 port 38128 ssh2
...
2020-04-16 07:45:15
148.59.185.117 attackbotsspam
1,47-11/04 [bc02/m70] PostRequest-Spammer scoring: stockholm
2020-04-16 07:35:49
118.69.53.104 attack
Automatic report - Port Scan Attack
2020-04-16 07:23:17
216.180.105.236 attack
(From lothian.winifred@hotmail.com) If you’ve been online any amount of time, you’re most likely still struggling to make the money you want online…

Am I right?

Well, we’re confident to say that you’ve come to the right place.

You might be thinking… Why are we different from the thousands of so-called “expert marketers” out there?

For one, I have the power to read your mind. I know exactly why you’re struggling right now...

OK - maybe reading your mind is a bit far fetched.

But what I can tell you is this…

We’ve worked with over 45,000+ customers.

And if they were struggling, we noticed it always came down to ONE important factor…

=>> http://bit.ly/UnlTraffic

You don't need to work for anyone else.

You don't need to take orders from your boss.

And you don't need to take permission to take vacation or spend a day with family.

And this is not just talk, let me show you real PROOF…

=>> http://bit.ly/UnlTraffic

Cheers
2020-04-16 07:31:27
94.25.8.218 attack
Unauthorised access (Apr 15) SRC=94.25.8.218 LEN=52 PREC=0x20 TTL=114 ID=23950 DF TCP DPT=445 WINDOW=8192 SYN
2020-04-16 07:27:22
65.97.0.208 attack
Invalid user serge from 65.97.0.208 port 33494
2020-04-16 07:22:28
148.70.149.39 attackspam
(sshd) Failed SSH login from 148.70.149.39 (CN/China/-): 5 in the last 3600 secs
2020-04-16 07:46:14
45.13.93.90 attackspambots
Apr 16 01:37:38 debian-2gb-nbg1-2 kernel: \[9252841.720204\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.13.93.90 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=54321 PROTO=TCP SPT=33564 DPT=8081 WINDOW=65535 RES=0x00 SYN URGP=0
2020-04-16 07:43:15
209.17.96.242 attackspambots
port scan and connect, tcp 22 (ssh)
2020-04-16 07:25:32

Recently Reported IPs

222.17.24.176 135.89.216.74 13.89.149.113 185.201.112.122
233.165.52.189 142.209.212.238 33.105.176.46 21.17.45.171
230.155.217.155 24.22.208.111 234.225.66.147 70.205.59.197
70.96.109.7 96.206.137.121 252.72.177.109 16.183.156.41
95.227.104.44 98.38.119.245 128.130.91.80 152.215.253.110