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

Region: New Jersey

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

;; QUESTION SECTION:
;104.109.153.130.		IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 14 17:42:10 CST 2022
;; MSG SIZE  rcvd: 108
Host info
130.153.109.104.in-addr.arpa domain name pointer a104-109-153-130.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
130.153.109.104.in-addr.arpa	name = a104-109-153-130.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
90.15.22.244 attack
" "
2019-10-23 03:47:44
188.226.182.209 attackspam
Oct 22 16:55:13 firewall sshd[21949]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.182.209
Oct 22 16:55:13 firewall sshd[21949]: Invalid user support2 from 188.226.182.209
Oct 22 16:55:15 firewall sshd[21949]: Failed password for invalid user support2 from 188.226.182.209 port 34088 ssh2
...
2019-10-23 03:58:42
117.81.232.68 attackbots
Unauthorized SMTP/IMAP/POP3 connection attempt
2019-10-23 03:50:43
170.80.224.240 attack
Oct 22 14:41:58 server sshd\[19069\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.80.224.240  user=root
Oct 22 14:42:00 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
Oct 22 14:42:03 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
Oct 22 14:42:04 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
Oct 22 14:42:06 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
...
2019-10-23 04:09:20
122.161.192.206 attackspambots
Oct 22 21:14:34 ArkNodeAT sshd\[9410\]: Invalid user andi123 from 122.161.192.206
Oct 22 21:14:34 ArkNodeAT sshd\[9410\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.161.192.206
Oct 22 21:14:36 ArkNodeAT sshd\[9410\]: Failed password for invalid user andi123 from 122.161.192.206 port 57856 ssh2
2019-10-23 04:06:20
203.205.21.110 attackbots
Unauthorised access (Oct 22) SRC=203.205.21.110 LEN=40 TTL=239 ID=46104 TCP DPT=1433 WINDOW=1024 SYN
2019-10-23 03:48:46
199.249.230.120 attackspam
Automatic report - XMLRPC Attack
2019-10-23 04:11:23
27.156.124.146 attack
Automatic report - FTP Brute Force
2019-10-23 04:10:14
112.105.151.65 attack
Honeypot attack, port: 23, PTR: 112-105-151-65.adsl.dynamic.seed.net.tw.
2019-10-23 04:02:46
61.175.194.90 attackspam
$f2bV_matches
2019-10-23 04:09:58
81.22.45.71 attack
10/22/2019-22:15:27.129052 81.22.45.71 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-10-23 04:16:40
185.144.120.9 attackbotsspam
MYH,DEF GET /wp-login.php
2019-10-23 03:58:14
188.254.0.170 attackbots
Oct 16 06:01:10 microserver sshd[57713]: Invalid user virendri from 188.254.0.170 port 56316
Oct 16 06:01:10 microserver sshd[57713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170
Oct 16 06:01:12 microserver sshd[57713]: Failed password for invalid user virendri from 188.254.0.170 port 56316 ssh2
Oct 16 06:04:36 microserver sshd[57902]: Invalid user yoshinari from 188.254.0.170 port 35498
Oct 16 06:04:36 microserver sshd[57902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170
Oct 16 06:15:11 microserver sshd[59603]: Invalid user tftpd from 188.254.0.170 port 57760
Oct 16 06:15:11 microserver sshd[59603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170
Oct 16 06:15:13 microserver sshd[59603]: Failed password for invalid user tftpd from 188.254.0.170 port 57760 ssh2
Oct 16 06:18:41 microserver sshd[59887]: Invalid user nr from 188.254.0.170 port 3694
2019-10-23 03:54:35
77.136.205.1 attack
Lines containing failures of 77.136.205.1
Oct 22 13:22:25 server01 postfix/smtpd[31976]: connect from 1.205.136.77.rev.sfr.net[77.136.205.1]
Oct x@x
Oct x@x
Oct 22 13:22:26 server01 postfix/policy-spf[31980]: : Policy action=550 Please see hxxp://www.openspf.org/Why?s=mfrom;id=aba4fae%40orisline.es;ip=77.136.205.1;r=server01.2800km.de
Oct x@x
Oct 22 13:22:26 server01 postfix/smtpd[31976]: lost connection after DATA from 1.205.136.77.rev.sfr.net[77.136.205.1]
Oct 22 13:22:26 server01 postfix/smtpd[31976]: disconnect from 1.205.136.77.rev.sfr.net[77.136.205.1]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=77.136.205.1
2019-10-23 03:45:10
183.173.113.248 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2019-10-23 04:05:54

Recently Reported IPs

104.109.152.126 104.109.155.148 104.109.156.202 104.11.88.190
104.110.243.10 104.110.243.17 104.111.41.169 104.112.235.89
104.114.73.178 104.114.73.216 104.117.43.91 104.117.44.100
104.117.49.94 104.117.51.30 104.120.138.112 104.120.138.16
104.120.138.65 104.120.138.72 104.123.196.136 104.124.131.15