城市(city): Hialeah
省份(region): Florida
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 104.0.0.0 - 104.15.255.255
CIDR: 104.0.0.0/12
NetName: SIS-80-1-6-2014
NetHandle: NET-104-0-0-0-1
Parent: NET104 (NET-104-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: AT&T Enterprises, LLC (AEL-360)
RegDate: 2014-01-16
Updated: 2024-12-05
Ref: https://rdap.arin.net/registry/ip/104.0.0.0
OrgName: AT&T Enterprises, LLC
OrgId: AEL-360
Address: 208 S. Akard St.
City: Dallas
StateProv: TX
PostalCode: 75202
Country: US
RegDate: 2024-11-22
Updated: 2025-10-29
Ref: https://rdap.arin.net/registry/entity/AEL-360
OrgTechHandle: ZS44-ARIN
OrgTechName: IPAdmin-ATT Internet Services
OrgTechPhone: +1-888-510-5545
OrgTechEmail: ipadmin@semail.att.com
OrgTechRef: https://rdap.arin.net/registry/entity/ZS44-ARIN
OrgTechHandle: ICC-ARIN
OrgTechName: IP Team
OrgTechPhone: +1-888-876-2382
OrgTechEmail: rm-ipspecialist@att.com
OrgTechRef: https://rdap.arin.net/registry/entity/ICC-ARIN
OrgAbuseHandle: ABUSE7-ARIN
OrgAbuseName: abuse
OrgAbusePhone: +1-919-319-8167
OrgAbuseEmail: abuse@att.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE7-ARIN
OrgRoutingHandle: ROUTI59-ARIN
OrgRoutingName: Routing POC
OrgRoutingPhone: +1-999-999-9999
OrgRoutingEmail: routing_poc@att.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ROUTI59-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.7.46.114
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4808
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.7.46.114. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026032400 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 24 16:30:39 CST 2026
;; MSG SIZE rcvd: 105114.46.7.104.in-addr.arpa domain name pointer 104-7-46-114.lightspeed.miamfl.sbcglobal.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
114.46.7.104.in-addr.arpa name = 104-7-46-114.lightspeed.miamfl.sbcglobal.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 78.16.202.206 | attackbots | Apr 21 06:58:42 mail sshd\[27735\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.16.202.206 user=root ... |
2020-04-21 19:03:58 |
| 106.13.189.158 | attack | SSH Brute-Force. Ports scanning. |
2020-04-21 18:56:49 |
| 94.69.60.159 | attack | Port probing on unauthorized port 8080 |
2020-04-21 18:46:21 |
| 110.136.4.146 | attack | Unauthorized connection attempt detected from IP address 110.136.4.146 to port 445 |
2020-04-21 19:08:57 |
| 111.167.187.70 | attack | Telnet/23 MH Probe, Scan, BF, Hack - |
2020-04-21 18:59:12 |
| 31.167.133.137 | attack | 2020-04-21T10:04:07.226339abusebot-3.cloudsearch.cf sshd[9464]: Invalid user kn from 31.167.133.137 port 52430 2020-04-21T10:04:07.233091abusebot-3.cloudsearch.cf sshd[9464]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.167.133.137 2020-04-21T10:04:07.226339abusebot-3.cloudsearch.cf sshd[9464]: Invalid user kn from 31.167.133.137 port 52430 2020-04-21T10:04:08.844280abusebot-3.cloudsearch.cf sshd[9464]: Failed password for invalid user kn from 31.167.133.137 port 52430 ssh2 2020-04-21T10:10:22.059520abusebot-3.cloudsearch.cf sshd[9771]: Invalid user sa from 31.167.133.137 port 35762 2020-04-21T10:10:22.069850abusebot-3.cloudsearch.cf sshd[9771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.167.133.137 2020-04-21T10:10:22.059520abusebot-3.cloudsearch.cf sshd[9771]: Invalid user sa from 31.167.133.137 port 35762 2020-04-21T10:10:23.827188abusebot-3.cloudsearch.cf sshd[9771]: Failed password for in ... |
2020-04-21 18:43:14 |
| 103.42.57.65 | attack | Apr 21 09:38:56 server sshd[22267]: Failed password for root from 103.42.57.65 port 40574 ssh2 Apr 21 09:43:21 server sshd[25552]: Failed password for invalid user test from 103.42.57.65 port 48030 ssh2 Apr 21 09:47:31 server sshd[28375]: Failed password for root from 103.42.57.65 port 55482 ssh2 |
2020-04-21 18:58:11 |
| 111.68.98.152 | attackspambots | Brute-force attempt banned |
2020-04-21 18:57:50 |
| 67.205.135.127 | attackspambots | Apr 20 19:39:57 sachi sshd\[1724\]: Invalid user iv from 67.205.135.127 Apr 20 19:39:57 sachi sshd\[1724\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.135.127 Apr 20 19:39:59 sachi sshd\[1724\]: Failed password for invalid user iv from 67.205.135.127 port 40046 ssh2 Apr 20 19:44:11 sachi sshd\[1997\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.135.127 user=root Apr 20 19:44:13 sachi sshd\[1997\]: Failed password for root from 67.205.135.127 port 59976 ssh2 |
2020-04-21 18:48:49 |
| 111.44.202.102 | attackspambots | 2020-04-2105:47:021jQjsA-0008DH-JV\<=info@whatsup2013.chH=\(localhost\)[111.44.202.102]:47652P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:info@whatsup2013.chS=3249id=a58eaffcf7dc09052267d18276b1cbc7f4247b92@whatsup2013.chT="NewlikereceivedfromTammi"forpascal16bachorb@gmail.comfunwork27@gmail.com2020-04-2105:47:371jQjsf-0008Eb-CM\<=info@whatsup2013.chH=\(localhost\)[96.30.70.192]:45227P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:info@whatsup2013.chS=3252id=0fb1faa9a2895c50773284d723e49e92a1c4769e@whatsup2013.chT="NewlikefromHolley"foralfredom459186@gmail.comjenkinstyler1217@gmail.com2020-04-2105:46:241jQjrb-0008Aj-WD\<=info@whatsup2013.chH=\(localhost\)[14.183.2.171]:58518P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:info@whatsup2013.chS=3023id=022395c6cde6ccc4585deb47a0240e12f9c63a@whatsup2013.chT="fromSullivantoleflot0871"forleflot0871@gmail.commanuelmarkau333@gmx.de2020-04-2105:46:371jQjro-0008Bw-Fm\<=info@whatsup2013.chH=171-10 |
2020-04-21 19:20:15 |
| 111.229.103.67 | attackspam | Apr 21 02:45:23 vps46666688 sshd[10166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.103.67 Apr 21 02:45:24 vps46666688 sshd[10166]: Failed password for invalid user ck from 111.229.103.67 port 41324 ssh2 ... |
2020-04-21 18:52:15 |
| 49.86.219.196 | attackspam | Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM - |
2020-04-21 19:18:47 |
| 124.156.121.233 | attackbotsspam | 2020-04-21T09:27:51.169074vps773228.ovh.net sshd[15124]: Invalid user docker from 124.156.121.233 port 51154 2020-04-21T09:27:51.181485vps773228.ovh.net sshd[15124]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.156.121.233 2020-04-21T09:27:51.169074vps773228.ovh.net sshd[15124]: Invalid user docker from 124.156.121.233 port 51154 2020-04-21T09:27:53.631943vps773228.ovh.net sshd[15124]: Failed password for invalid user docker from 124.156.121.233 port 51154 ssh2 2020-04-21T09:34:48.144918vps773228.ovh.net sshd[15240]: Invalid user ubuntu from 124.156.121.233 port 42682 ... |
2020-04-21 18:44:29 |
| 51.79.55.141 | attackspambots | Fail2Ban Ban Triggered (2) |
2020-04-21 19:00:44 |
| 217.217.90.149 | attack | Apr 21 14:32:55 webhost01 sshd[6580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.217.90.149 Apr 21 14:32:58 webhost01 sshd[6580]: Failed password for invalid user test from 217.217.90.149 port 55563 ssh2 ... |
2020-04-21 18:56:32 |