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

Region: Kansas

Country: United States

Internet Service Provider: AT&T

Hostname: unknown

Organization: AT&T Services, Inc.

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

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

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sun Jun 02 21:37:59 CST 2019
;; MSG SIZE  rcvd: 117

Host info
37.39.180.104.in-addr.arpa domain name pointer 104-180-39-37.lightspeed.wchtks.sbcglobal.net.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
37.39.180.104.in-addr.arpa	name = 104-180-39-37.lightspeed.wchtks.sbcglobal.net.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
192.227.252.28 attackbotsspam
SSH bruteforce
2019-09-29 17:08:57
197.95.193.173 attackbotsspam
SSH Brute Force
2019-09-29 17:35:42
113.248.24.12 attackspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-09-29 17:26:47
117.35.74.206 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-09-29 17:31:42
114.35.76.71 attack
Sep 29 05:44:41 mc1 kernel: \[1015111.337099\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=114.35.76.71 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=54454 PROTO=TCP SPT=35225 DPT=23 WINDOW=21880 RES=0x00 SYN URGP=0 
Sep 29 05:47:47 mc1 kernel: \[1015297.420342\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=114.35.76.71 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=54454 PROTO=TCP SPT=35225 DPT=23 WINDOW=21880 RES=0x00 SYN URGP=0 
Sep 29 05:49:11 mc1 kernel: \[1015380.801765\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=114.35.76.71 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=54454 PROTO=TCP SPT=35225 DPT=23 WINDOW=21880 RES=0x00 SYN URGP=0 
...
2019-09-29 17:32:18
117.121.100.228 attackspambots
Sep 29 01:27:55 plusreed sshd[24432]: Invalid user user1 from 117.121.100.228
...
2019-09-29 17:46:09
220.135.50.222 attackspam
Sep 28 23:46:21 localhost kernel: [3466600.122914] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.135.50.222 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=47 ID=26458 PROTO=TCP SPT=50214 DPT=23 WINDOW=61974 RES=0x00 SYN URGP=0 
Sep 28 23:46:21 localhost kernel: [3466600.122938] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.135.50.222 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=47 ID=26458 PROTO=TCP SPT=50214 DPT=23 SEQ=758669438 ACK=0 WINDOW=61974 RES=0x00 SYN URGP=0 
Sep 28 23:49:27 localhost kernel: [3466786.118934] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.135.50.222 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=47 ID=26458 PROTO=TCP SPT=50214 DPT=23 WINDOW=61974 RES=0x00 SYN URGP=0 
Sep 28 23:49:27 localhost kernel: [3466786.118940] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.135.50.222 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x
2019-09-29 17:20:36
114.246.11.178 attackbotsspam
Sep 29 08:36:19 localhost sshd\[10158\]: Invalid user vu from 114.246.11.178 port 49186
Sep 29 08:36:19 localhost sshd\[10158\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.246.11.178
Sep 29 08:36:21 localhost sshd\[10158\]: Failed password for invalid user vu from 114.246.11.178 port 49186 ssh2
2019-09-29 17:09:28
77.123.154.234 attackspam
Sep 28 18:48:07 web1 sshd\[30208\]: Invalid user weng from 77.123.154.234
Sep 28 18:48:07 web1 sshd\[30208\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.123.154.234
Sep 28 18:48:09 web1 sshd\[30208\]: Failed password for invalid user weng from 77.123.154.234 port 37365 ssh2
Sep 28 18:52:21 web1 sshd\[30560\]: Invalid user xbian from 77.123.154.234
Sep 28 18:52:21 web1 sshd\[30560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.123.154.234
2019-09-29 17:22:51
93.114.77.11 attackspambots
2019-09-29T07:41:57.775535tmaserv sshd\[8125\]: Failed password for invalid user tiscali from 93.114.77.11 port 52802 ssh2
2019-09-29T07:55:21.049752tmaserv sshd\[8696\]: Invalid user max from 93.114.77.11 port 32966
2019-09-29T07:55:21.053654tmaserv sshd\[8696\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.114.77.11
2019-09-29T07:55:23.587894tmaserv sshd\[8696\]: Failed password for invalid user max from 93.114.77.11 port 32966 ssh2
2019-09-29T07:59:48.978306tmaserv sshd\[8899\]: Invalid user sv from 93.114.77.11 port 45178
2019-09-29T07:59:48.982604tmaserv sshd\[8899\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.114.77.11
...
2019-09-29 17:09:56
106.12.120.155 attack
Sep 29 11:09:29 tux-35-217 sshd\[14178\]: Invalid user asterisk from 106.12.120.155 port 49378
Sep 29 11:09:29 tux-35-217 sshd\[14178\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.120.155
Sep 29 11:09:31 tux-35-217 sshd\[14178\]: Failed password for invalid user asterisk from 106.12.120.155 port 49378 ssh2
Sep 29 11:15:20 tux-35-217 sshd\[14199\]: Invalid user dz from 106.12.120.155 port 60908
Sep 29 11:15:20 tux-35-217 sshd\[14199\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.120.155
...
2019-09-29 17:45:21
185.168.127.209 attackbotsspam
Sep 29 07:47:30 core sshd[10231]: Invalid user 12345 from 185.168.127.209 port 50100
Sep 29 07:47:31 core sshd[10231]: Failed password for invalid user 12345 from 185.168.127.209 port 50100 ssh2
...
2019-09-29 17:25:04
182.18.188.132 attackspambots
Sep 29 07:07:35 www2 sshd\[60612\]: Failed password for list from 182.18.188.132 port 39968 ssh2Sep 29 07:11:27 www2 sshd\[61137\]: Invalid user dw from 182.18.188.132Sep 29 07:11:28 www2 sshd\[61137\]: Failed password for invalid user dw from 182.18.188.132 port 56388 ssh2
...
2019-09-29 17:19:07
54.36.150.84 attackbots
Automated report (2019-09-29T03:48:41+00:00). Scraper detected at this address.
2019-09-29 17:50:07
183.6.43.105 attackbots
Sep 29 12:16:17 server sshd\[2956\]: Invalid user ivory from 183.6.43.105 port 55954
Sep 29 12:16:17 server sshd\[2956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.43.105
Sep 29 12:16:19 server sshd\[2956\]: Failed password for invalid user ivory from 183.6.43.105 port 55954 ssh2
Sep 29 12:21:46 server sshd\[25401\]: Invalid user dorjan from 183.6.43.105 port 39790
Sep 29 12:21:46 server sshd\[25401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.43.105
2019-09-29 17:27:37

Recently Reported IPs

90.54.56.217 195.29.30.238 198.67.212.72 181.45.80.161
122.224.235.215 186.84.174.136 157.108.34.228 111.202.220.8
79.219.209.122 17.154.159.231 3.49.132.61 119.241.60.163
134.110.88.68 103.251.175.253 103.97.179.181 190.219.53.131
41.165.187.50 105.112.99.111 60.138.9.40 177.244.39.50