City: unknown
Region: unknown
Country: United States
Internet Service Provider: 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-2025, American Registry for Internet Numbers, Ltd.
#
NetRange: 4.0.0.0 - 4.127.255.255
CIDR: 4.0.0.0/9
NetName: LVLT-ORG-4-8
NetHandle: NET-4-0-0-0-1
Parent: NET4 (NET-4-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Level 3 Parent, LLC (LPL-141)
RegDate: 1992-12-01
Updated: 2019-07-17
Ref: https://rdap.arin.net/registry/ip/4.0.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: 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/LPL-141
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
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
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-2025, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 4.99.216.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26224
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;4.99.216.48. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025101200 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 12 18:29:14 CST 2025
;; MSG SIZE rcvd: 104b'Host 48.216.99.4.in-addr.arpa. not found: 3(NXDOMAIN)
'Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 48.216.99.4.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 195.78.63.197 | attackbots | Nov 25 23:46:09 * sshd[27217]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.78.63.197 Nov 25 23:46:11 * sshd[27217]: Failed password for invalid user doree from 195.78.63.197 port 57565 ssh2 |
2019-11-26 07:37:59 |
| 50.70.229.239 | attack | Lines containing failures of 50.70.229.239 Nov 25 19:26:13 *** sshd[72698]: Invalid user jacob from 50.70.229.239 port 39168 Nov 25 19:26:13 *** sshd[72698]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.70.229.239 Nov 25 19:26:15 *** sshd[72698]: Failed password for invalid user jacob from 50.70.229.239 port 39168 ssh2 Nov 25 19:26:15 *** sshd[72698]: Received disconnect from 50.70.229.239 port 39168:11: Bye Bye [preauth] Nov 25 19:26:15 *** sshd[72698]: Disconnected from invalid user jacob 50.70.229.239 port 39168 [preauth] Nov 25 19:54:00 *** sshd[74184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=50.70.229.239 user=r.r Nov 25 19:54:02 *** sshd[74184]: Failed password for r.r from 50.70.229.239 port 45052 ssh2 Nov 25 19:54:03 *** sshd[74184]: Received disconnect from 50.70.229.239 port 45052:11: Bye Bye [preauth] Nov 25 19:54:03 *** sshd[74184]: Disconnected from authenticating ........ ------------------------------ |
2019-11-26 07:06:28 |
| 46.38.144.57 | attackbotsspam | Nov 26 00:09:32 webserver postfix/smtpd\[5797\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 26 00:10:19 webserver postfix/smtpd\[5797\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 26 00:11:05 webserver postfix/smtpd\[5797\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 26 00:11:53 webserver postfix/smtpd\[5797\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 26 00:12:40 webserver postfix/smtpd\[5116\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-11-26 07:32:34 |
| 192.155.94.53 | attackbots | Nov 25 18:16:57 ny01 sshd[30358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.155.94.53 Nov 25 18:16:59 ny01 sshd[30358]: Failed password for invalid user rpc from 192.155.94.53 port 47928 ssh2 Nov 25 18:23:10 ny01 sshd[30905]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.155.94.53 |
2019-11-26 07:38:28 |
| 125.25.215.94 | attackspam | port scan/probe/communication attempt; port 23 |
2019-11-26 07:05:32 |
| 192.228.100.98 | attack | 2019-11-25 dovecot_login authenticator failed for \(USER\) \[192.228.100.98\]: 535 Incorrect authentication data \(set_id=noauth@miplounge.net\) 2019-11-25 dovecot_login authenticator failed for \(USER\) \[192.228.100.98\]: 535 Incorrect authentication data \(set_id=noauth@**REMOVED**.eu\) 2019-11-25 dovecot_login authenticator failed for \(USER\) \[192.228.100.98\]: 535 Incorrect authentication data \(set_id=noauth@**REMOVED**.org\) |
2019-11-26 07:27:06 |
| 119.29.121.229 | attackspam | Nov 25 13:20:03 php1 sshd\[15636\]: Invalid user guest from 119.29.121.229 Nov 25 13:20:03 php1 sshd\[15636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.121.229 Nov 25 13:20:05 php1 sshd\[15636\]: Failed password for invalid user guest from 119.29.121.229 port 39706 ssh2 Nov 25 13:26:55 php1 sshd\[16199\]: Invalid user apple from 119.29.121.229 Nov 25 13:26:55 php1 sshd\[16199\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.121.229 |
2019-11-26 07:40:27 |
| 193.70.37.140 | attack | 2019-11-25T23:24:11.061718host3.slimhost.com.ua sshd[1492027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.ip-193-70-37.eu user=games 2019-11-25T23:24:13.747726host3.slimhost.com.ua sshd[1492027]: Failed password for games from 193.70.37.140 port 37496 ssh2 2019-11-25T23:40:38.911745host3.slimhost.com.ua sshd[1498097]: Invalid user laten from 193.70.37.140 port 43426 2019-11-25T23:40:38.918905host3.slimhost.com.ua sshd[1498097]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.ip-193-70-37.eu 2019-11-25T23:40:38.911745host3.slimhost.com.ua sshd[1498097]: Invalid user laten from 193.70.37.140 port 43426 2019-11-25T23:40:40.440499host3.slimhost.com.ua sshd[1498097]: Failed password for invalid user laten from 193.70.37.140 port 43426 ssh2 2019-11-25T23:46:25.442456host3.slimhost.com.ua sshd[1500228]: Invalid user usbmux from 193.70.37.140 port 50958 2019-11-25T23:46:25.447326host3.slimhost.com.ua ... |
2019-11-26 07:28:59 |
| 188.32.85.234 | attackspambots | Nov 26 01:46:48 server sshd\[5865\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=broadband-188-32-85-234.ip.moscow.rt.ru user=root Nov 26 01:46:50 server sshd\[5865\]: Failed password for root from 188.32.85.234 port 38622 ssh2 Nov 26 01:46:52 server sshd\[5865\]: Failed password for root from 188.32.85.234 port 38622 ssh2 Nov 26 01:46:54 server sshd\[5865\]: Failed password for root from 188.32.85.234 port 38622 ssh2 Nov 26 01:46:56 server sshd\[5865\]: Failed password for root from 188.32.85.234 port 38622 ssh2 ... |
2019-11-26 07:05:15 |
| 210.12.215.225 | attackbotsspam | Nov 25 16:02:31 shadeyouvpn sshd[21724]: Invalid user zenz from 210.12.215.225 Nov 25 16:02:31 shadeyouvpn sshd[21724]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.12.215.225 Nov 25 16:02:33 shadeyouvpn sshd[21724]: Failed password for invalid user zenz from 210.12.215.225 port 47733 ssh2 Nov 25 16:02:33 shadeyouvpn sshd[21724]: Received disconnect from 210.12.215.225: 11: Bye Bye [preauth] Nov 25 16:28:54 shadeyouvpn sshd[8530]: Received disconnect from 210.12.215.225: 11: Bye Bye [preauth] Nov 25 16:32:57 shadeyouvpn sshd[11167]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.12.215.225 user=r.r Nov 25 16:32:59 shadeyouvpn sshd[11167]: Failed password for r.r from 210.12.215.225 port 42283 ssh2 Nov 25 16:32:59 shadeyouvpn sshd[11167]: Received disconnect from 210.12.215.225: 11: Bye Bye [preauth] Nov 25 16:37:17 shadeyouvpn sshd[15418]: Invalid user carline from 210.12.215.2........ ------------------------------- |
2019-11-26 07:27:57 |
| 222.186.180.6 | attackspam | Brute-force attempt banned |
2019-11-26 07:07:52 |
| 222.186.175.169 | attackspam | Nov 26 00:15:09 legacy sshd[868]: Failed password for root from 222.186.175.169 port 61076 ssh2 Nov 26 00:15:22 legacy sshd[868]: error: maximum authentication attempts exceeded for root from 222.186.175.169 port 61076 ssh2 [preauth] Nov 26 00:15:27 legacy sshd[883]: Failed password for root from 222.186.175.169 port 6288 ssh2 ... |
2019-11-26 07:20:42 |
| 62.219.50.252 | attackspam | Nov 26 00:05:59 tuxlinux sshd[62004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.219.50.252 user=root Nov 26 00:06:01 tuxlinux sshd[62004]: Failed password for root from 62.219.50.252 port 45322 ssh2 Nov 26 00:05:59 tuxlinux sshd[62004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.219.50.252 user=root Nov 26 00:06:01 tuxlinux sshd[62004]: Failed password for root from 62.219.50.252 port 45322 ssh2 Nov 26 00:06:03 tuxlinux sshd[62017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.219.50.252 user=bin ... |
2019-11-26 07:19:08 |
| 188.120.239.34 | attackbots | Nov 25 00:26:01 : SSH login attempts with invalid user |
2019-11-26 07:27:31 |
| 123.51.152.54 | attackspam | 2019-11-25T23:12:25.504364abusebot-5.cloudsearch.cf sshd\[31420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.51.152.54 user=root |
2019-11-26 07:31:54 |