城市(city): unknown
省份(region): unknown
国家(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: 207.220.0.0 - 207.220.255.255
CIDR: 207.220.0.0/16
NetName: LPL-141
NetHandle: NET-207-220-0-0-1
Parent: NET207 (NET-207-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Level 3 Parent, LLC (LPL-141)
RegDate: 2024-11-25
Updated: 2024-12-06
Ref: https://rdap.arin.net/registry/ip/207.220.0.0
OrgName: Level 3 Parent, LLC
OrgId: LPL-141
Address: 100 CenturyLink Drive
City: Monroe
StateProv: LA
PostalCode: 71203
Country: US
RegDate: 2018-02-06
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/LPL-141
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
OrgTechHandle: APL7-ARIN
OrgTechName: ADMIN POC LVLT
OrgTechPhone: +1-877-453-8353
OrgTechEmail: ipadmin@centurylink.com
OrgTechRef: https://rdap.arin.net/registry/entity/APL7-ARIN
OrgAbuseHandle: LAC56-ARIN
OrgAbuseName: L3 Abuse Contact
OrgAbusePhone: +1-877-453-8353
OrgAbuseEmail: abuse@level3.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/LAC56-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 <<>> 207.220.179.163
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44161
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;207.220.179.163. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026092101 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 22 06:41:20 CST 2026
;; MSG SIZE rcvd: 108Host 163.179.220.207.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 163.179.220.207.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 95.160.169.83 | attackbots | Jun 8 22:56:05 serwer sshd\[5078\]: Invalid user angel from 95.160.169.83 port 57824 Jun 8 22:56:05 serwer sshd\[5078\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.160.169.83 Jun 8 22:56:07 serwer sshd\[5078\]: Failed password for invalid user angel from 95.160.169.83 port 57824 ssh2 ... |
2020-06-09 06:32:54 |
| 185.160.27.69 | attack | Jun 8 05:13:20 DNS-2 sshd[18117]: User r.r from 185.160.27.69 not allowed because not listed in AllowUsers Jun 8 05:13:20 DNS-2 sshd[18117]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.160.27.69 user=r.r Jun 8 05:13:22 DNS-2 sshd[18117]: Failed password for invalid user r.r from 185.160.27.69 port 47840 ssh2 Jun 8 05:13:24 DNS-2 sshd[18117]: Received disconnect from 185.160.27.69 port 47840:11: Bye Bye [preauth] Jun 8 05:13:24 DNS-2 sshd[18117]: Disconnected from invalid user r.r 185.160.27.69 port 47840 [preauth] Jun 8 05:29:18 DNS-2 sshd[18173]: User r.r from 185.160.27.69 not allowed because not listed in AllowUsers Jun 8 05:29:18 DNS-2 sshd[18173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.160.27.69 user=r.r Jun 8 05:29:20 DNS-2 sshd[18173]: Failed password for invalid user r.r from 185.160.27.69 port 41234 ssh2 Jun 8 05:29:20 DNS-2 sshd[18173]: Received disc........ ------------------------------- |
2020-06-09 06:18:28 |
| 115.159.198.41 | attackbotsspam | web-1 [ssh_2] SSH Attack |
2020-06-09 06:27:45 |
| 192.35.169.41 | attack | Hits on port : 9049 |
2020-06-09 06:13:31 |
| 183.196.118.205 | attackspambots | IP 183.196.118.205 attacked honeypot on port: 139 at 6/8/2020 9:24:53 PM |
2020-06-09 06:10:42 |
| 189.181.207.76 | attack | Automatic report - XMLRPC Attack |
2020-06-09 06:17:41 |
| 13.68.185.213 | attackspambots | Jun 8 22:20:23 rush sshd[16435]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.68.185.213 Jun 8 22:20:25 rush sshd[16435]: Failed password for invalid user write from 13.68.185.213 port 53818 ssh2 Jun 8 22:24:30 rush sshd[16543]: Failed password for root from 13.68.185.213 port 35230 ssh2 ... |
2020-06-09 06:39:35 |
| 80.211.230.69 | attack | Jun 8 23:57:41 [host] sshd[23874]: pam_unix(sshd: Jun 8 23:57:43 [host] sshd[23874]: Failed passwor Jun 9 00:01:21 [host] sshd[24002]: pam_unix(sshd: |
2020-06-09 06:40:39 |
| 106.53.102.196 | attackspam | no |
2020-06-09 06:32:23 |
| 222.186.175.182 | attack | Hit honeypot r. |
2020-06-09 06:12:46 |
| 106.13.147.69 | attack | Jun 8 22:21:26 prod4 sshd\[3427\]: Failed password for root from 106.13.147.69 port 60080 ssh2 Jun 8 22:24:49 prod4 sshd\[4438\]: Invalid user raghum from 106.13.147.69 Jun 8 22:24:50 prod4 sshd\[4438\]: Failed password for invalid user raghum from 106.13.147.69 port 43752 ssh2 ... |
2020-06-09 06:26:24 |
| 107.189.10.93 | attack | 2020-06-08 15:23:02.892375-0500 localhost sshd[3786]: Failed password for root from 107.189.10.93 port 33816 ssh2 |
2020-06-09 06:11:09 |
| 122.14.47.18 | attackspambots | Jun 8 22:24:51 host sshd[14030]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.14.47.18 user=root Jun 8 22:24:53 host sshd[14030]: Failed password for root from 122.14.47.18 port 17957 ssh2 ... |
2020-06-09 06:21:56 |
| 2.38.43.232 | attack | Automatic report - Banned IP Access |
2020-06-09 06:08:18 |
| 188.166.78.16 | attackspam | SASL PLAIN auth failed: ruser=... |
2020-06-09 06:17:54 |