12.204.130.16 - IPInfo

Basic Info

City: Battle Creek

Region: Michigan

Country: United States

Internet Service Provider: AT&T

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:

No discussion about this subnet yet..

Whois info:

Dig info:

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

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

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 31 08:13:37 CST 2020
;; MSG SIZE  rcvd: 117

Host info

Host 16.130.204.12.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

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

Related IP info:

Related comments:

IP	Type	Details	Datetime
119.146.145.104	attackspambots	Nov 2 19:42:32 hanapaa sshd\[29713\]: Invalid user odroid from 119.146.145.104 Nov 2 19:42:32 hanapaa sshd\[29713\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.146.145.104 Nov 2 19:42:34 hanapaa sshd\[29713\]: Failed password for invalid user odroid from 119.146.145.104 port 2137 ssh2 Nov 2 19:49:02 hanapaa sshd\[30235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.146.145.104 user=root Nov 2 19:49:05 hanapaa sshd\[30235\]: Failed password for root from 119.146.145.104 port 2138 ssh2	2019-11-03 19:24:56
51.38.153.207	attackbots	Nov 3 11:32:58 v22018076622670303 sshd\[27056\]: Invalid user pass from 51.38.153.207 port 49454 Nov 3 11:32:58 v22018076622670303 sshd\[27056\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.153.207 Nov 3 11:33:00 v22018076622670303 sshd\[27056\]: Failed password for invalid user pass from 51.38.153.207 port 49454 ssh2 ...	2019-11-03 19:30:19
149.202.214.11	attackbots	Nov 3 06:51:50 vps647732 sshd[25926]: Failed password for root from 149.202.214.11 port 59956 ssh2 Nov 3 06:55:35 vps647732 sshd[25957]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.214.11 ...	2019-11-03 19:44:11
218.92.0.189	attack	Nov 3 11:41:58 amit sshd\[17352\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.189 user=root Nov 3 11:42:01 amit sshd\[17352\]: Failed password for root from 218.92.0.189 port 16779 ssh2 Nov 3 11:42:03 amit sshd\[17352\]: Failed password for root from 218.92.0.189 port 16779 ssh2 ...	2019-11-03 19:58:15
188.80.22.177	attackspam	fail2ban honeypot	2019-11-03 19:43:53
51.38.129.120	attack	Nov 3 04:19:51 ny01 sshd[18160]: Failed password for root from 51.38.129.120 port 60354 ssh2 Nov 3 04:23:14 ny01 sshd[18476]: Failed password for root from 51.38.129.120 port 39646 ssh2	2019-11-03 19:52:33
86.120.62.75	attack	/editBlackAndWhiteList	2019-11-03 19:56:05
185.176.27.94	attackbotsspam	11/03/2019-12:00:54.059059 185.176.27.94 Protocol: 6 ET DROP Dshield Block Listed Source group 1	2019-11-03 19:34:41
88.214.26.20	attackbots	191103 10:53:59 \[Warning\] Access denied for user 'admin'@'88.214.26.20' \(using password: YES\) 191103 11:00:34 \[Warning\] Access denied for user 'admin'@'88.214.26.20' \(using password: YES\) 191103 13:14:52 \[Warning\] Access denied for user 'admin'@'88.214.26.20' \(using password: YES\) ...	2019-11-03 19:58:42
27.154.225.186	attackbotsspam	Nov 3 11:35:08 server sshd\[6829\]: Invalid user vnc from 27.154.225.186 Nov 3 11:35:08 server sshd\[6829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.154.225.186 Nov 3 11:35:10 server sshd\[6829\]: Failed password for invalid user vnc from 27.154.225.186 port 44468 ssh2 Nov 3 11:59:15 server sshd\[12492\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.154.225.186 user=root Nov 3 11:59:16 server sshd\[12492\]: Failed password for root from 27.154.225.186 port 36910 ssh2 ...	2019-11-03 19:38:46
125.64.94.220	attackspam	firewall-block, port(s): 8999/tcp	2019-11-03 19:54:39
138.68.92.121	attack	Nov 3 11:40:15 icinga sshd[3710]: Failed password for root from 138.68.92.121 port 46176 ssh2 Nov 3 11:45:36 icinga sshd[4203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.92.121 ...	2019-11-03 19:31:02
93.131.70.79	attackspam	Nov 3 06:47:39 server1 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.131.70.79, lip=185.151.203.50, session=\\ Nov 3 06:47:39 server1 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.131.70.79, lip=185.151.203.50, session=\\ Nov 3 06:47:39 server1 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.131.70.79, lip=185.151.203.50, session=\\ Nov 3 06:47:39 server1 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=93.131.70.79, lip=185.151.203.50, session=\\ Nov 3 06:47:45 server1 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 6 secs\): user=\, method=PLAIN, rip=93.131.70.79, lip=185.151.203.50, ses	2019-11-03 19:55:08
140.143.58.46	attackspam	Nov 3 11:15:39 root sshd[4073]: Failed password for root from 140.143.58.46 port 52008 ssh2 Nov 3 11:34:48 root sshd[4220]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.58.46 Nov 3 11:34:50 root sshd[4220]: Failed password for invalid user webmaster from 140.143.58.46 port 50234 ssh2 ...	2019-11-03 19:42:38
107.152.176.47	attackbotsspam	(From francoedward98@gmail.com) Hi! Did you know that the first page of Goggle search results is where all potential clients will be looking at if they're searching for products/services? Does your website appear on the first page of Google search results when you try searching for your products/services? Most of the time, they would just ignore page 2 and so on since the results listed on the first page seem more relevant and are more credible. I'm very familiar with all the algorithms and methods that search engines use and I am an expert on how to get the most out of it. I'm a freelance online marketing specialist, and I have helped my clients bring their websites to the first page of web searches for more than 10 years now. Also, the cost of my services is something that small businesses can afford. I can give you a free consultation so you can be better informed of how your website is doing right now, what can be done and what to expect after if this is something that interests you. Kindly write	2019-11-03 19:45:50

Recently Reported IPs

12.245.237.60	100.16.68.135	178.210.205.215	219.2.53.99
72.69.39.139	109.81.73.57	157.25.219.154	85.158.112.149
12.116.133.200	137.17.170.255	121.121.91.109	173.95.169.3
160.72.158.188	61.173.254.249	88.234.66.58	186.0.166.213
105.162.60.137	180.247.86.13	162.238.13.90	109.64.10.10