必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): Monte Vista

省份(region): Colorado

国家(country): United States

运营商(isp): RTC Communications LLC

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
#
# 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信息:
; <<>> 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信息:
Host 29.39.169.205.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 29.39.169.205.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
218.92.0.180 attack
Jul 23 11:48:02 microserver sshd[56973]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.180  user=root
Jul 23 11:48:04 microserver sshd[56973]: Failed password for root from 218.92.0.180 port 60158 ssh2
Jul 23 11:48:07 microserver sshd[56973]: Failed password for root from 218.92.0.180 port 60158 ssh2
Jul 23 11:48:10 microserver sshd[56973]: Failed password for root from 218.92.0.180 port 60158 ssh2
Jul 23 11:48:13 microserver sshd[56973]: Failed password for root from 218.92.0.180 port 60158 ssh2
Jul 24 14:01:34 microserver sshd[42087]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.180  user=root
Jul 24 14:01:36 microserver sshd[42087]: Failed password for root from 218.92.0.180 port 39987 ssh2
Jul 24 14:01:39 microserver sshd[42087]: Failed password for root from 218.92.0.180 port 39987 ssh2
Jul 24 14:01:41 microserver sshd[42087]: Failed password for root from 218.92.0.180 port 39987 ssh2
Jul 24 14:01:44 mi
2019-09-21 09:07:22
177.23.196.77 attackspam
Sep 21 06:50:45 site3 sshd\[198161\]: Invalid user teamspeak from 177.23.196.77
Sep 21 06:50:45 site3 sshd\[198161\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.196.77
Sep 21 06:50:48 site3 sshd\[198161\]: Failed password for invalid user teamspeak from 177.23.196.77 port 56858 ssh2
Sep 21 06:56:30 site3 sshd\[198349\]: Invalid user dream from 177.23.196.77
Sep 21 06:56:30 site3 sshd\[198349\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.196.77
...
2019-09-21 12:17:11
177.37.77.64 attackspambots
2019-09-21T00:58:15.511264abusebot-7.cloudsearch.cf sshd\[12664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.37.77.64  user=root
2019-09-21 09:05:12
49.88.112.80 attackbots
SSH Brute Force, server-1 sshd[20279]: Failed password for root from 49.88.112.80 port 56141 ssh2
2019-09-21 09:15:56
81.47.128.178 attackbotsspam
Sep 20 17:57:17 hcbb sshd\[6169\]: Invalid user 123Admin from 81.47.128.178
Sep 20 17:57:17 hcbb sshd\[6169\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.red-81-47-128.staticip.rima-tde.net
Sep 20 17:57:19 hcbb sshd\[6169\]: Failed password for invalid user 123Admin from 81.47.128.178 port 50944 ssh2
Sep 20 18:01:12 hcbb sshd\[6506\]: Invalid user teamspeak4 from 81.47.128.178
Sep 20 18:01:12 hcbb sshd\[6506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.red-81-47-128.staticip.rima-tde.net
2019-09-21 12:07:16
51.68.44.158 attackspam
Sep 20 18:07:59 hanapaa sshd\[10402\]: Invalid user dmin from 51.68.44.158
Sep 20 18:07:59 hanapaa sshd\[10402\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.ip-51-68-44.eu
Sep 20 18:08:01 hanapaa sshd\[10402\]: Failed password for invalid user dmin from 51.68.44.158 port 56824 ssh2
Sep 20 18:11:44 hanapaa sshd\[10858\]: Invalid user d from 51.68.44.158
Sep 20 18:11:44 hanapaa sshd\[10858\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.ip-51-68-44.eu
2019-09-21 12:17:30
34.67.30.226 attackspam
Sep 20 15:11:45 php1 sshd\[1512\]: Invalid user dodi from 34.67.30.226
Sep 20 15:11:45 php1 sshd\[1512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.67.30.226
Sep 20 15:11:48 php1 sshd\[1512\]: Failed password for invalid user dodi from 34.67.30.226 port 46046 ssh2
Sep 20 15:15:46 php1 sshd\[1946\]: Invalid user support from 34.67.30.226
Sep 20 15:15:46 php1 sshd\[1946\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.67.30.226
2019-09-21 09:16:20
181.120.97.114 attackbotsspam
TCP Port: 25 _    invalid blocked  abuseat-org also barracudacentral _  _  _ _ (1434)
2019-09-21 09:06:16
51.254.33.188 attackbots
Sep 21 02:22:12 SilenceServices sshd[8216]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.33.188
Sep 21 02:22:14 SilenceServices sshd[8216]: Failed password for invalid user acct from 51.254.33.188 port 49074 ssh2
Sep 21 02:26:00 SilenceServices sshd[10646]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.33.188
2019-09-21 09:18:21
81.171.107.56 attack
\[2019-09-20 23:56:20\] NOTICE\[2270\] chan_sip.c: Registration from '\' failed for '81.171.107.56:62606' - Wrong password
\[2019-09-20 23:56:20\] SECURITY\[2283\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-09-20T23:56:20.173-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="9311",SessionID="0x7fcd8c1c4788",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/81.171.107.56/62606",Challenge="079bc03c",ReceivedChallenge="079bc03c",ReceivedHash="754d3e83c5bd0bd48a1dc51d6c4265ef"
\[2019-09-20 23:56:37\] NOTICE\[2270\] chan_sip.c: Registration from '\' failed for '81.171.107.56:53306' - Wrong password
\[2019-09-20 23:56:37\] SECURITY\[2283\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-09-20T23:56:37.972-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="959",SessionID="0x7fcd8c21d098",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/81.171.107.
2019-09-21 12:13:29
101.251.72.205 attackspam
Sep 20 23:24:29 vps691689 sshd[29611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.251.72.205
Sep 20 23:24:31 vps691689 sshd[29611]: Failed password for invalid user user from 101.251.72.205 port 34915 ssh2
...
2019-09-21 09:13:31
198.50.200.80 attackbots
Sep 20 18:09:02 sachi sshd\[16647\]: Invalid user centos from 198.50.200.80
Sep 20 18:09:02 sachi sshd\[16647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip80.ip-198-50-200.net
Sep 20 18:09:04 sachi sshd\[16647\]: Failed password for invalid user centos from 198.50.200.80 port 38596 ssh2
Sep 20 18:13:15 sachi sshd\[17089\]: Invalid user gmodserver from 198.50.200.80
Sep 20 18:13:15 sachi sshd\[17089\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip80.ip-198-50-200.net
2019-09-21 12:18:12
118.193.80.106 attackbotsspam
Sep 21 04:14:58 localhost sshd\[63218\]: Invalid user caixa from 118.193.80.106 port 41847
Sep 21 04:14:58 localhost sshd\[63218\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.193.80.106
Sep 21 04:15:00 localhost sshd\[63218\]: Failed password for invalid user caixa from 118.193.80.106 port 41847 ssh2
Sep 21 04:19:43 localhost sshd\[63355\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.193.80.106  user=root
Sep 21 04:19:45 localhost sshd\[63355\]: Failed password for root from 118.193.80.106 port 33743 ssh2
...
2019-09-21 12:24:37
54.36.150.104 attackbots
Automatic report - Banned IP Access
2019-09-21 12:21:02
203.129.226.99 attack
Sep 20 20:13:24 vps647732 sshd[7063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.129.226.99
Sep 20 20:13:26 vps647732 sshd[7063]: Failed password for invalid user 0123456789 from 203.129.226.99 port 1767 ssh2
...
2019-09-21 09:14:26

最近上报的IP列表

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