城市(city): Las Vegas
省份(region): Nevada
国家(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: 71.32.0.0 - 71.39.255.255
CIDR: 71.32.0.0/13
NetName: CENTURYLINK-LEGACY-QWEST-INET-119
NetHandle: NET-71-32-0-0-1
Parent: NET71 (NET-71-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: CenturyLink Communications, LLC (CCL-534)
RegDate: 2004-12-17
Updated: 2018-10-04
Ref: https://rdap.arin.net/registry/ip/71.32.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: 2024-06-17
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
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
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
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 <<>> 71.38.228.237
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44660
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;71.38.228.237. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026041400 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Apr 14 15:56:49 CST 2026
;; MSG SIZE rcvd: 106
237.228.38.71.in-addr.arpa domain name pointer 71-38-228-237.lsv2.qwest.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
237.228.38.71.in-addr.arpa name = 71-38-228-237.lsv2.qwest.net.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 138.94.210.50 | attackbotsspam | Distributed brute force attack |
2019-07-27 02:56:55 |
| 138.197.103.160 | attackbotsspam | Jul 26 14:19:13 vps200512 sshd\[3872\]: Invalid user fileshare from 138.197.103.160 Jul 26 14:19:13 vps200512 sshd\[3872\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.103.160 Jul 26 14:19:15 vps200512 sshd\[3872\]: Failed password for invalid user fileshare from 138.197.103.160 port 58616 ssh2 Jul 26 14:23:35 vps200512 sshd\[3976\]: Invalid user zhou from 138.197.103.160 Jul 26 14:23:35 vps200512 sshd\[3976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.103.160 |
2019-07-27 03:14:17 |
| 167.99.75.174 | attackbots | Jul 26 07:25:52 debian sshd[25438]: Unable to negotiate with 167.99.75.174 port 34854: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth] Jul 26 14:28:57 debian sshd[16800]: Unable to negotiate with 167.99.75.174 port 55470: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth] ... |
2019-07-27 03:29:01 |
| 5.238.181.44 | attackbotsspam | Jul 26 10:38:53 h2034429 postfix/smtpd[20408]: connect from unknown[5.238.181.44] Jul x@x Jul 26 10:38:54 h2034429 postfix/smtpd[20408]: lost connection after DATA from unknown[5.238.181.44] Jul 26 10:38:54 h2034429 postfix/smtpd[20408]: disconnect from unknown[5.238.181.44] ehlo=1 mail=1 rcpt=0/1 data=0/1 commands=2/4 Jul 26 10:39:09 h2034429 postfix/smtpd[20408]: connect from unknown[5.238.181.44] Jul x@x Jul 26 10:39:10 h2034429 postfix/smtpd[20408]: lost connection after DATA from unknown[5.238.181.44] Jul 26 10:39:10 h2034429 postfix/smtpd[20408]: disconnect from unknown[5.238.181.44] ehlo=1 mail=1 rcpt=0/1 data=0/1 commands=2/4 Jul 26 10:39:21 h2034429 postfix/smtpd[20408]: connect from unknown[5.238.181.44] Jul x@x Jul 26 10:39:22 h2034429 postfix/smtpd[20408]: lost connection after DATA from unknown[5.238.181.44] Jul 26 10:39:22 h2034429 postfix/smtpd[20408]: disconnect from unknown[5.238.181.44] ehlo=1 mail=1 rcpt=0/1 data=0/1 commands=2/4 ........ ----------------------------------------------- ht |
2019-07-27 03:03:50 |
| 186.31.65.66 | attackspambots | Jul 26 14:13:37 vps200512 sshd\[3749\]: Invalid user xp from 186.31.65.66 Jul 26 14:13:37 vps200512 sshd\[3749\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.31.65.66 Jul 26 14:13:39 vps200512 sshd\[3749\]: Failed password for invalid user xp from 186.31.65.66 port 3329 ssh2 Jul 26 14:18:34 vps200512 sshd\[3862\]: Invalid user yu from 186.31.65.66 Jul 26 14:18:34 vps200512 sshd\[3862\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.31.65.66 |
2019-07-27 03:28:07 |
| 201.22.95.52 | attackspambots | SSH Brute Force |
2019-07-27 03:03:22 |
| 192.99.216.184 | attackspambots | Jul 26 21:05:05 yabzik sshd[9823]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.216.184 Jul 26 21:05:07 yabzik sshd[9823]: Failed password for invalid user fo from 192.99.216.184 port 37789 ssh2 Jul 26 21:09:23 yabzik sshd[11267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.216.184 |
2019-07-27 02:58:45 |
| 78.158.131.52 | attack | Netgear DGN Device Remote Command Execution Vulnerability, PTR: cpe-668076.ip.primehome.com. |
2019-07-27 03:27:39 |
| 190.183.222.39 | attackspam | Jul 26 18:54:57 debian sshd\[13608\]: Invalid user brian from 190.183.222.39 port 47510 Jul 26 18:54:57 debian sshd\[13608\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.183.222.39 ... |
2019-07-27 02:48:35 |
| 206.189.65.11 | attack | 2019-07-26T18:33:23.663532abusebot.cloudsearch.cf sshd\[543\]: Invalid user mysql from 206.189.65.11 port 52636 |
2019-07-27 02:53:02 |
| 134.209.61.78 | attackbotsspam | 2019-07-26T18:36:22.121297Z 1e5c9ef3243d New connection: 134.209.61.78:59772 (172.17.0.3:2222) [session: 1e5c9ef3243d] 2019-07-26T18:48:27.807430Z 867ff86ce60d New connection: 134.209.61.78:52798 (172.17.0.3:2222) [session: 867ff86ce60d] |
2019-07-27 03:08:55 |
| 114.237.109.125 | attack | Jul 26 11:51:57 elektron postfix/smtpd\[31641\]: NOQUEUE: reject: RCPT from unknown\[114.237.109.125\]: 450 4.7.1 Client host rejected: cannot find your hostname, \[114.237.109.125\]\; from=\ |
2019-07-27 03:31:33 |
| 113.160.158.129 | attackspambots | SSH-bruteforce attempts |
2019-07-27 03:19:56 |
| 89.121.46.43 | attackspam | Honeypot triggered via portsentry |
2019-07-27 03:37:01 |
| 185.139.21.48 | attackspam | Jul 26 09:52:29 ip-172-31-1-72 sshd\[18572\]: Invalid user yckim from 185.139.21.48 Jul 26 09:52:29 ip-172-31-1-72 sshd\[18572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.139.21.48 Jul 26 09:52:31 ip-172-31-1-72 sshd\[18572\]: Failed password for invalid user yckim from 185.139.21.48 port 55102 ssh2 Jul 26 09:52:38 ip-172-31-1-72 sshd\[18575\]: Invalid user 123 from 185.139.21.48 Jul 26 09:52:38 ip-172-31-1-72 sshd\[18575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.139.21.48 |
2019-07-27 03:20:17 |