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: unknown

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-2025, 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


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

# 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


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

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

# 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-2025, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 205.169.39.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30151
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;205.169.39.0.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Dec 10 22:31:18 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 0.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 0.39.169.205.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
77.247.110.216 attackspambots
\[2019-08-25 06:54:46\] NOTICE\[1829\] chan_sip.c: Registration from '"2008" \' failed for '77.247.110.216:5986' - Wrong password
\[2019-08-25 06:54:46\] SECURITY\[1837\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-08-25T06:54:46.229-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="2008",SessionID="0x7f7b30fa67f8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247.110.216/5986",Challenge="4064dba8",ReceivedChallenge="4064dba8",ReceivedHash="db61e56e7cfea54dba79efe0f6bc6541"
\[2019-08-25 06:54:46\] NOTICE\[1829\] chan_sip.c: Registration from '"2008" \' failed for '77.247.110.216:5986' - Wrong password
\[2019-08-25 06:54:46\] SECURITY\[1837\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-08-25T06:54:46.381-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="2008",SessionID="0x7f7b304de1f8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4
2019-08-25 19:38:05
206.189.221.160 attackspambots
Aug 24 21:57:39 php2 sshd\[20338\]: Invalid user webadmin from 206.189.221.160
Aug 24 21:57:39 php2 sshd\[20338\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=desligar.me
Aug 24 21:57:41 php2 sshd\[20338\]: Failed password for invalid user webadmin from 206.189.221.160 port 44666 ssh2
Aug 24 22:01:50 php2 sshd\[20814\]: Invalid user postgres from 206.189.221.160
Aug 24 22:01:50 php2 sshd\[20814\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=desligar.me
2019-08-25 20:06:29
37.139.21.75 attack
Aug 25 10:56:59 gitlab-tf sshd\[9046\]: Invalid user nicholas from 37.139.21.75Aug 25 11:01:34 gitlab-tf sshd\[10116\]: Invalid user oracle from 37.139.21.75
...
2019-08-25 19:43:07
186.208.221.98 attackspam
Unauthorized connection attempt from IP address 186.208.221.98 on Port 445(SMB)
2019-08-25 19:53:31
123.207.196.160 attack
Aug 25 09:04:31 ip-172-31-1-72 sshd\[11486\]: Invalid user test from 123.207.196.160
Aug 25 09:04:31 ip-172-31-1-72 sshd\[11486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.196.160
Aug 25 09:04:33 ip-172-31-1-72 sshd\[11486\]: Failed password for invalid user test from 123.207.196.160 port 56380 ssh2
Aug 25 09:08:11 ip-172-31-1-72 sshd\[11532\]: Invalid user chocolateslim from 123.207.196.160
Aug 25 09:08:11 ip-172-31-1-72 sshd\[11532\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.196.160
2019-08-25 20:03:59
185.175.93.18 attackspambots
08/25/2019-08:01:00.338658 185.175.93.18 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-25 20:21:02
93.87.82.78 attack
Unauthorized connection attempt from IP address 93.87.82.78 on Port 445(SMB)
2019-08-25 20:24:05
129.211.125.167 attackbots
Aug 25 01:29:02 lcdev sshd\[1957\]: Invalid user web2 from 129.211.125.167
Aug 25 01:29:02 lcdev sshd\[1957\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.125.167
Aug 25 01:29:03 lcdev sshd\[1957\]: Failed password for invalid user web2 from 129.211.125.167 port 33079 ssh2
Aug 25 01:34:52 lcdev sshd\[2447\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.125.167  user=root
Aug 25 01:34:54 lcdev sshd\[2447\]: Failed password for root from 129.211.125.167 port 54365 ssh2
2019-08-25 19:51:35
137.74.26.179 attackbotsspam
Aug 25 14:52:32 lcl-usvr-01 sshd[14846]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.26.179  user=mysql
Aug 25 14:52:33 lcl-usvr-01 sshd[14846]: Failed password for mysql from 137.74.26.179 port 48832 ssh2
Aug 25 15:01:53 lcl-usvr-01 sshd[17517]: Invalid user ian from 137.74.26.179
Aug 25 15:01:53 lcl-usvr-01 sshd[17517]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.26.179 
Aug 25 15:01:53 lcl-usvr-01 sshd[17517]: Invalid user ian from 137.74.26.179
Aug 25 15:01:55 lcl-usvr-01 sshd[17517]: Failed password for invalid user ian from 137.74.26.179 port 53686 ssh2
2019-08-25 19:56:02
92.47.92.196 attackspam
Unauthorized connection attempt from IP address 92.47.92.196 on Port 445(SMB)
2019-08-25 20:28:21
185.153.196.191 attackspam
Port scan on 6 port(s): 1081 1087 7009 13000 21000 36000
2019-08-25 20:25:38
180.156.30.107 attack
Unauthorized connection attempt from IP address 180.156.30.107 on Port 445(SMB)
2019-08-25 19:44:41
62.148.142.202 attack
Aug 25 02:23:54 eddieflores sshd\[893\]: Invalid user test3 from 62.148.142.202
Aug 25 02:23:54 eddieflores sshd\[893\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=rus.ktng.ru
Aug 25 02:23:56 eddieflores sshd\[893\]: Failed password for invalid user test3 from 62.148.142.202 port 33048 ssh2
Aug 25 02:28:33 eddieflores sshd\[1278\]: Invalid user game from 62.148.142.202
Aug 25 02:28:33 eddieflores sshd\[1278\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=rus.ktng.ru
2019-08-25 20:29:08
85.192.35.167 attackspambots
Aug 25 02:04:02 tdfoods sshd\[19359\]: Invalid user seij from 85.192.35.167
Aug 25 02:04:02 tdfoods sshd\[19359\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.192.35.167
Aug 25 02:04:04 tdfoods sshd\[19359\]: Failed password for invalid user seij from 85.192.35.167 port 51784 ssh2
Aug 25 02:08:22 tdfoods sshd\[19835\]: Invalid user Victor from 85.192.35.167
Aug 25 02:08:22 tdfoods sshd\[19835\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.192.35.167
2019-08-25 20:18:08
14.141.147.230 attackbotsspam
19/8/25@04:02:04: FAIL: Alarm-Intrusion address from=14.141.147.230
...
2019-08-25 19:49:23

Recently Reported IPs

103.191.15.151 103.127.219.59 2.58.56.55 91.25.109.227
216.36.96.207 167.172.177.125 81.94.156.226 135.237.126.203
39.144.162.230 180.178.57.74 34.231.195.239 221.207.34.189
28.76.5.176 142.93.199.16 5.180.186.61 1.82.133.130
100.30.248.17 83.4.161.145 47.84.99.214 47.237.80.102