城市(city): Billings
省份(region): Montana
国家(country): United States
运营商(isp): RTC Communications LLC
主机名(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: 63.152.0.0 - 63.159.255.255
CIDR: 63.152.0.0/13
NetName: CENTURYLINK-LEGACY-QWEST-INET-16
NetHandle: NET-63-152-0-0-1
Parent: NET63 (NET-63-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: CenturyLink Communications, LLC (CCL-534)
RegDate: 2000-07-12
Updated: 2018-02-21
Ref: https://rdap.arin.net/registry/ip/63.152.0.0
OrgName: CenturyLink Communications, LLC
OrgId: CCL-534
Address: 100 CENTURYLINK DR
City: Monroe
StateProv: LA
PostalCode: 71201
Country: US
RegDate: 2018-07-12
Updated: 2026-04-22
Comment: USAGE OF IP SPACE MUST COMPLY WITH OUR ACCEPTABLE USE POLICY:
Comment: https://www.lumen.com/en-us/about/legal/acceptable-use-policy.html
Comment:
Comment: ADDRESSES COVERED BY THIS ORG-ID ARE NON-PORTABLE ANY ISP ANNOUNCING OR TRANSITING PORTIONS WITHIN OUR RANGES SHOULD NOT RELY ON PRESENTED LOA'S OR OLD WHOIS UNLESS THOSE RANGES ARE ALSO ACTIVELY DIRECTLY ANNOUNCED TO A LUMEN ASN. WITH ALL LOA'S THESE CONDITIONS APPLY:
Comment:
Comment: 1. You are permitted to route the Lumen IP prefixes listed via Public BGP to your alternate ISP from the designated ASN. Any other ASN originating the prefix listed is forbidden.
Comment: 2. The Lumen IP prefixes listed can be routed via Public BGP to your alternate ISP as long as you remain an active customer with Lumen and continue to route the prefixes over at least one Lumen Internet circuit without significant traffic engineering.
Comment: 3. Should your Internet services with Lumen be discontinued, Lumen reserves the right to have your alternate ISP terminate the routing of the Lumen IP prefixes without advanced notification, should you fail to do so.
Comment: 4. All IP Addresses assigned or allocated by Lumen to an end-user (customer or ISP) shall be considered non-portable and will be reclaimed by Lumen upon service termination.
Comment: 5. Lumen reserves the right to conduct audits to ensure the LOA conditions are being met.
Comment: 6. Usage of IP space must comply with our AUP https://www.lumen.com/en-us/about/legal/acceptable-use-policy.html
Comment:
Comment: Our looking glass is located at: https://lookingglass.centurylink.com/
Comment:
Comment: For subpoena or court order please fax 844.254.5800 or refer to our Trust & Safety page:
Comment: https://www.lumen.com/en-us/about/legal/trust-center/trust-and-safety.html
Comment:
Comment: For abuse issues, please email abuse@aup.lumen.com
Comment: All abuse reports MUST include:
Comment: * src IP
Comment: * dest IP (your IP)
Comment: * dest port
Comment: * Accurate date/timestamp and timezone of activity
Comment: * Intensity/frequency (short log extracts)
Comment: * Your contact details (phone and email)
Comment: Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref: https://rdap.arin.net/registry/entity/CCL-534
OrgAbuseHandle: CAD54-ARIN
OrgAbuseName: Centurylink Abuse Desk
OrgAbusePhone: +1-877-886-6515
OrgAbuseEmail: abuse@aup.lumen.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/CAD54-ARIN
OrgTechHandle: QIA-ARIN
OrgTechName: Centurylink IP Admin
OrgTechPhone: +1-877-886-6515
OrgTechEmail: ipadmin@centurylink.com
OrgTechRef: https://rdap.arin.net/registry/entity/QIA-ARIN
OrgRoutingHandle: RPKIR-ARIN
OrgRoutingName: RPKI-ROA
OrgRoutingPhone: +1-877-886-6515
OrgRoutingEmail: rpki-roa@lumen.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/RPKIR-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 <<>> 63.158.236.216
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10000
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;63.158.236.216. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026081601 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Aug 17 06:53:13 CST 2026
;; MSG SIZE rcvd: 107
216.236.158.63.in-addr.arpa domain name pointer 63-158-236-216.dia.static.qwest.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
216.236.158.63.in-addr.arpa name = 63-158-236-216.dia.static.qwest.net.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 115.159.3.221 | attackspambots | Jan 6 05:07:58 wbs sshd\[22796\]: Invalid user bd from 115.159.3.221 Jan 6 05:07:58 wbs sshd\[22796\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.3.221 Jan 6 05:08:00 wbs sshd\[22796\]: Failed password for invalid user bd from 115.159.3.221 port 37194 ssh2 Jan 6 05:11:28 wbs sshd\[23214\]: Invalid user seiwhat from 115.159.3.221 Jan 6 05:11:28 wbs sshd\[23214\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.3.221 |
2020-01-06 23:30:55 |
| 1.82.194.216 | attackspambots | Unauthorized connection attempt detected from IP address 1.82.194.216 to port 81 [T] |
2020-01-07 00:02:30 |
| 125.129.26.238 | attack | Invalid user tester from 125.129.26.238 port 47958 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.129.26.238 Failed password for invalid user tester from 125.129.26.238 port 47958 ssh2 Invalid user intro from 125.129.26.238 port 40048 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.129.26.238 |
2020-01-06 23:30:19 |
| 138.68.105.194 | attackbotsspam | Unauthorized connection attempt detected from IP address 138.68.105.194 to port 2220 [J] |
2020-01-06 23:35:57 |
| 157.245.206.139 | attack | "GET /kcfinder/upload.php HTTP/1.1" 404 "GET /admin/kcfinder/upload.php HTTP/1.1" 404 "GET /plugins/kcfinder/upload.php HTTP/1.1" 404 |
2020-01-06 23:42:58 |
| 47.96.91.14 | attackbots | Unauthorized connection attempt detected from IP address 47.96.91.14 to port 6379 [J] |
2020-01-07 00:01:09 |
| 217.219.70.155 | attackspambots | 01/06/2020-08:12:54.026969 217.219.70.155 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2020-01-06 23:40:54 |
| 89.248.168.112 | attack | Unauthorized connection attempt detected from IP address 89.248.168.112 to port 1723 [T] |
2020-01-06 23:59:19 |
| 180.180.48.34 | attack | 20/1/6@09:40:38: FAIL: Alarm-Network address from=180.180.48.34 20/1/6@09:40:39: FAIL: Alarm-Network address from=180.180.48.34 ... |
2020-01-06 23:39:20 |
| 218.92.0.184 | attackspambots | Jan 6 11:40:04 server sshd\[910\]: Failed password for root from 218.92.0.184 port 30467 ssh2 Jan 6 18:25:46 server sshd\[31096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.184 user=root Jan 6 18:25:48 server sshd\[31096\]: Failed password for root from 218.92.0.184 port 58926 ssh2 Jan 6 18:25:51 server sshd\[31096\]: Failed password for root from 218.92.0.184 port 58926 ssh2 Jan 6 18:25:54 server sshd\[31096\]: Failed password for root from 218.92.0.184 port 58926 ssh2 ... |
2020-01-06 23:43:40 |
| 180.176.212.93 | attack | Unauthorized connection attempt detected from IP address 180.176.212.93 to port 4567 [J] |
2020-01-07 00:04:31 |
| 180.167.16.82 | attackspambots | Unauthorized connection attempt detected from IP address 180.167.16.82 to port 22 [T] |
2020-01-07 00:04:44 |
| 183.80.89.146 | attack | Unauthorized connection attempt detected from IP address 183.80.89.146 to port 23 [T] |
2020-01-07 00:03:49 |
| 120.253.197.229 | attackspambots | Unauthorized connection attempt detected from IP address 120.253.197.229 to port 23 [J] |
2020-01-07 00:07:42 |
| 115.82.6.100 | attackbots | Unauthorized connection attempt detected from IP address 115.82.6.100 to port 445 [T] |
2020-01-06 23:58:23 |