Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Monte Vista

Region: Colorado

Country: United States

Internet Service Provider: RTC Communications LLC

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
#
# 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.
#



# start

NetRange:       205.168.0.0 - 205.171.255.255
CIDR:           205.168.0.0/14
NetName:        CENTURYLINK-LEGACY-QWEST-INET-35
NetHandle:      NET-205-168-0-0-1
Parent:         NET205 (NET-205-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   CenturyLink Communications, LLC (CCL-534)
RegDate:        1995-03-17
Updated:        2018-02-21
Ref:            https://rdap.arin.net/registry/ip/205.168.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


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

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

# end


# start

NetRange:       205.169.39.0 - 205.169.39.255
CIDR:           205.169.39.0/24
NetName:        LOANED-SPACE-TO-PALO-ALTO
NetHandle:      NET-205-169-39-0-1
Parent:         CENTURYLINK-LEGACY-QWEST-INET-35 (NET-205-168-0-0-1)
NetType:        Reassigned
OriginAS:       
Organization:   Palo Alto Networks, Inc (PAN-22)
RegDate:        2025-12-01
Updated:        2025-12-01
Ref:            https://rdap.arin.net/registry/ip/205.169.39.0



OrgName:        Palo Alto Networks, Inc
OrgId:          PAN-22
Address:        Palo Alto Networks
Address:        3000 Tannery Way
Address:        Santa Clara, CA 95054
City:           Santa Clara
StateProv:      CA
PostalCode:     95054
Country:        US
RegDate:        2017-11-22
Updated:        2024-11-25
Ref:            https://rdap.arin.net/registry/entity/PAN-22


OrgAbuseHandle: IPABU42-ARIN
OrgAbuseName:   IP Abuse
OrgAbusePhone:  +1-408-753-4000 
OrgAbuseEmail:  dl-ipabuse@paloaltonetworks.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/IPABU42-ARIN

OrgTechHandle: GNS20-ARIN
OrgTechName:   Global Network Services 
OrgTechPhone:  +1-408-753-4000 
OrgTechEmail:  gns-prod@paloaltonetworks.com
OrgTechRef:    https://rdap.arin.net/registry/entity/GNS20-ARIN

# end



#
# 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 info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 205.169.39.29
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8760
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;205.169.39.29.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026032501 1800 900 604800 86400

;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 26 04:30:19 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 29.39.169.205.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 29.39.169.205.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
58.221.204.114 attackspambots
May  6 22:20:30 [host] sshd[21692]: pam_unix(sshd:
May  6 22:20:33 [host] sshd[21692]: Failed passwor
May  6 22:23:03 [host] sshd[21809]: Invalid user h
2020-05-07 04:50:55
222.186.180.147 attackbots
May  6 22:06:32 combo sshd[29099]: Failed password for root from 222.186.180.147 port 5406 ssh2
May  6 22:06:35 combo sshd[29099]: Failed password for root from 222.186.180.147 port 5406 ssh2
May  6 22:06:39 combo sshd[29099]: Failed password for root from 222.186.180.147 port 5406 ssh2
...
2020-05-07 05:06:54
111.67.195.165 attack
May  6 22:48:53 legacy sshd[12844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.195.165
May  6 22:48:55 legacy sshd[12844]: Failed password for invalid user xjt from 111.67.195.165 port 52786 ssh2
May  6 22:52:46 legacy sshd[13028]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.195.165
...
2020-05-07 05:02:37
141.98.81.84 attackspambots
May  6 22:53:04 sxvn sshd[631155]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.81.84
2020-05-07 05:19:22
178.73.215.171 attack
firewall-block, port(s): 5900/tcp
2020-05-07 05:01:57
217.199.140.254 attackspambots
May  6 22:10:45 lock-38 sshd[2026069]: Disconnected from invalid user testuser 217.199.140.254 port 48080 [preauth]
May  6 22:23:00 lock-38 sshd[2026429]: Invalid user hja from 217.199.140.254 port 46797
May  6 22:23:00 lock-38 sshd[2026429]: Invalid user hja from 217.199.140.254 port 46797
May  6 22:23:00 lock-38 sshd[2026429]: Failed password for invalid user hja from 217.199.140.254 port 46797 ssh2
May  6 22:23:00 lock-38 sshd[2026429]: Disconnected from invalid user hja 217.199.140.254 port 46797 [preauth]
...
2020-05-07 04:52:16
60.248.249.190 attackbotsspam
(imapd) Failed IMAP login from 60.248.249.190 (TW/Taiwan/60-248-249-190.HINET-IP.hinet.net): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: May  7 00:52:41 ir1 dovecot[264309]: imap-login: Disconnected (auth failed, 1 attempts in 5 secs): user=, method=PLAIN, rip=60.248.249.190, lip=5.63.12.44, TLS, session=
2020-05-07 05:09:52
222.186.175.150 attackbotsspam
May  6 22:50:34 vpn01 sshd[4981]: Failed password for root from 222.186.175.150 port 49494 ssh2
May  6 22:50:38 vpn01 sshd[4981]: Failed password for root from 222.186.175.150 port 49494 ssh2
...
2020-05-07 05:06:27
222.186.190.14 attack
May  6 23:00:09 amit sshd\[7206\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.14  user=root
May  6 23:00:11 amit sshd\[7206\]: Failed password for root from 222.186.190.14 port 21737 ssh2
May  6 23:03:53 amit sshd\[883\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.14  user=root
...
2020-05-07 05:05:25
201.122.102.21 attackbots
May  6 22:11:16 lock-38 sshd[2026092]: Disconnected from authenticating user root 201.122.102.21 port 42616 [preauth]
May  6 22:24:03 lock-38 sshd[2026493]: Invalid user vlc from 201.122.102.21 port 42980
May  6 22:24:03 lock-38 sshd[2026493]: Invalid user vlc from 201.122.102.21 port 42980
May  6 22:24:03 lock-38 sshd[2026493]: Failed password for invalid user vlc from 201.122.102.21 port 42980 ssh2
May  6 22:24:03 lock-38 sshd[2026493]: Disconnected from invalid user vlc 201.122.102.21 port 42980 [preauth]
...
2020-05-07 05:09:01
201.48.34.195 attackspam
SSH Brute-Force attacks
2020-05-07 04:46:16
218.232.135.95 attackbots
May  6 22:50:24 eventyay sshd[24506]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.232.135.95
May  6 22:50:26 eventyay sshd[24506]: Failed password for invalid user support from 218.232.135.95 port 60174 ssh2
May  6 22:54:23 eventyay sshd[24599]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.232.135.95
...
2020-05-07 04:54:33
162.243.137.169 attack
" "
2020-05-07 05:22:32
218.92.0.208 attack
May  6 22:48:13 eventyay sshd[24430]: Failed password for root from 218.92.0.208 port 24958 ssh2
May  6 22:49:17 eventyay sshd[24458]: Failed password for root from 218.92.0.208 port 18093 ssh2
...
2020-05-07 04:56:55
142.93.137.144 attack
May  6 22:47:35 server sshd[25142]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.137.144
May  6 22:47:37 server sshd[25142]: Failed password for invalid user ao from 142.93.137.144 port 53330 ssh2
May  6 22:51:07 server sshd[25397]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.137.144
...
2020-05-07 04:57:35

Recently Reported IPs

46.101.82.104 202.58.242.20 66.132.186.202 120.124.229.26
44.204.184.42 44.202.13.116 3.90.5.174 20.74.212.144
185.242.3.64 110.78.156.191 2606:4700:10::6814:7662 2606:4700:10::6814:7215
2606:4700:10::6816:3590 2606:4700:10::6816:476 2606:4700:10::6814:5572 110.78.138.189
2606:4700:10::6814:4926 2606:4700:10::6816:4581 2606:4700:10::6814:9702 2606:4700:10::6816:3123