221.13.12.242 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: None

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
221.13.12.79	attack	Unauthorized connection attempt detected from IP address 221.13.12.79 to port 123	2020-06-13 06:05:18
221.13.12.19	attack	Web Server Scan. RayID: 592aa77abd9b0256, UA: Mozilla/4.049897920 Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729), Country: CN	2020-05-21 03:47:26
221.13.12.222	attackspam	China's GFW probe	2020-05-15 17:35:44
221.13.12.235	attack	Unauthorized connection attempt detected from IP address 221.13.12.235 to port 992 [T]	2020-04-15 02:25:36
221.13.12.179	attackspam	Unauthorized connection attempt detected from IP address 221.13.12.179 to port 3389 [J]	2020-03-03 02:05:51
221.13.12.142	attackspam	Unauthorized connection attempt detected from IP address 221.13.12.142 to port 8899 [J]	2020-03-02 20:47:11
221.13.12.187	attack	Unauthorized connection attempt detected from IP address 221.13.12.187 to port 22 [J]	2020-03-02 19:21:12
221.13.12.104	attackbots	Unauthorized connection attempt detected from IP address 221.13.12.104 to port 22 [J]	2020-03-02 17:29:07
221.13.12.65	attack	Unauthorized connection attempt detected from IP address 221.13.12.65 to port 8081 [J]	2020-03-02 16:58:59
221.13.12.133	attackspam	Unauthorized connection attempt detected from IP address 221.13.12.133 to port 8082 [J]	2020-03-02 16:29:37
221.13.12.98	attack	Unauthorized connection attempt detected from IP address 221.13.12.98 to port 8118 [J]	2020-03-02 14:47:39
221.13.12.91	attack	Unauthorized connection attempt detected from IP address 221.13.12.91 to port 8000 [J]	2020-03-02 14:14:42
221.13.12.97	attackbots	Unauthorized connection attempt detected from IP address 221.13.12.97 to port 8443 [J]	2020-02-05 09:04:55
221.13.12.118	attackbots	Unauthorized connection attempt detected from IP address 221.13.12.118 to port 443 [J]	2020-01-31 22:42:35
221.13.12.224	attackspam	Unauthorized connection attempt detected from IP address 221.13.12.224 to port 9011 [T]	2020-01-29 10:16:31

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 221.13.12.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38078
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;221.13.12.242.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 11:23:17 CST 2022
;; MSG SIZE  rcvd: 106

Host info

b'Host 242.12.13.221.in-addr.arpa not found: 2(SERVFAIL)
'

Nslookup info:

;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 242.12.13.221.in-addr.arpa: SERVFAIL

Related IP info:

Related comments:

IP	Type	Details	Datetime
45.146.203.115	attackbots	$f2bV_matches	2019-11-06 00:00:30
194.36.174.15	attack	SSH invalid-user multiple login try	2019-11-05 23:38:20
45.82.153.76	attackbotsspam	2019-11-05 16:30:33 dovecot_login authenticator failed for $\[45.82.153.76\]$ \[45.82.153.76\]: 535 Incorrect authentication data $set_id=info@opso.it$ 2019-11-05 16:30:42 dovecot_login authenticator failed for $\[45.82.153.76\]$ \[45.82.153.76\]: 535 Incorrect authentication data 2019-11-05 16:30:53 dovecot_login authenticator failed for $\[45.82.153.76\]$ \[45.82.153.76\]: 535 Incorrect authentication data 2019-11-05 16:30:59 dovecot_login authenticator failed for $\[45.82.153.76\]$ \[45.82.153.76\]: 535 Incorrect authentication data 2019-11-05 16:31:13 dovecot_login authenticator failed for $\[45.82.153.76\]$ \[45.82.153.76\]: 535 Incorrect authentication data	2019-11-05 23:32:51
51.91.136.174	attackbots	2019-11-05T15:18:01.649966abusebot-5.cloudsearch.cf sshd\[27174\]: Invalid user ubuntu from 51.91.136.174 port 51366	2019-11-05 23:28:51
103.82.32.7	attackspam	Message ID Created at: Tue, Nov 5, 2019 at 8:39 AM (Delivered after -1 seconds) From: HavenLock Offer To: me@cisco.com.uk Subject: Are you safe in your own home? SPF: SOFTFAIL with IP 103.82.32.7	2019-11-05 23:48:28
222.143.242.66	attack	Nov 5 15:34:34 icinga sshd[32178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.143.242.66 Nov 5 15:34:36 icinga sshd[32178]: Failed password for invalid user support from 222.143.242.66 port 41777 ssh2 Nov 5 15:43:23 icinga sshd[40109]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.143.242.66 ...	2019-11-05 23:58:52
192.188.2.235	attackbotsspam	1433	2019-11-06 00:01:02
37.57.103.177	attackspam	2019-11-05T15:46:37.731247shield sshd\[5693\]: Invalid user wubao from 37.57.103.177 port 53572 2019-11-05T15:46:37.739481shield sshd\[5693\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.57.103.177 2019-11-05T15:46:40.022941shield sshd\[5693\]: Failed password for invalid user wubao from 37.57.103.177 port 53572 ssh2 2019-11-05T15:51:03.799544shield sshd\[6125\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.57.103.177 user=root 2019-11-05T15:51:05.265188shield sshd\[6125\]: Failed password for root from 37.57.103.177 port 37194 ssh2	2019-11-05 23:57:31
81.22.45.159	attack	11/05/2019-09:40:57.922357 81.22.45.159 Protocol: 6 ET DROP Dshield Block Listed Source group 1	2019-11-05 23:44:52
106.12.16.140	attackbotsspam	2019-11-05T15:20:20.498688abusebot-6.cloudsearch.cf sshd\[22838\]: Invalid user vps from 106.12.16.140 port 48062	2019-11-05 23:50:42
182.162.143.236	attackbots	2019-11-05T15:41:26.146129abusebot-5.cloudsearch.cf sshd\[27410\]: Invalid user keith from 182.162.143.236 port 46344	2019-11-05 23:57:18
134.209.7.179	attackspambots	Nov 5 15:27:23 hcbbdb sshd\[8191\]: Invalid user 1 from 134.209.7.179 Nov 5 15:27:23 hcbbdb sshd\[8191\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.7.179 Nov 5 15:27:25 hcbbdb sshd\[8191\]: Failed password for invalid user 1 from 134.209.7.179 port 40544 ssh2 Nov 5 15:31:20 hcbbdb sshd\[8595\]: Invalid user Password from 134.209.7.179 Nov 5 15:31:20 hcbbdb sshd\[8595\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.7.179	2019-11-05 23:34:24
109.123.117.254	attackspam	DNS Enumeration	2019-11-05 23:40:22
36.110.217.169	attackbots	Nov 5 15:40:31 ns41 sshd[4825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.110.217.169	2019-11-05 23:59:55
182.151.37.230	attackspambots	2019-11-05T15:11:40.130203shield sshd\[1427\]: Invalid user nexus from 182.151.37.230 port 50094 2019-11-05T15:11:40.134517shield sshd\[1427\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.151.37.230 2019-11-05T15:11:41.535148shield sshd\[1427\]: Failed password for invalid user nexus from 182.151.37.230 port 50094 ssh2 2019-11-05T15:17:51.003656shield sshd\[2336\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.151.37.230 user=root 2019-11-05T15:17:52.865878shield sshd\[2336\]: Failed password for root from 182.151.37.230 port 58126 ssh2	2019-11-05 23:31:25

Recently Reported IPs

221.14.171.35	221.15.253.109	221.197.28.189	221.15.176.226
221.176.205.230	221.159.193.138	221.15.253.50	221.14.197.51
221.15.228.124	221.198.81.35	221.198.83.207	221.207.76.108
221.200.77.174	221.213.75.213	221.215.15.196	221.215.184.174
221.219.102.6	221.221.149.69	221.218.136.132	221.221.148.198