必须是合法有效的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


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

;; QUESTION SECTION:
;205.169.39.54.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 28 16:01:01 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 54.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 54.39.169.205.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
83.9.214.45 attackbotsspam
Apr 16 06:57:36 santamaria sshd\[5175\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.9.214.45  user=root
Apr 16 06:57:39 santamaria sshd\[5175\]: Failed password for root from 83.9.214.45 port 42230 ssh2
Apr 16 07:04:19 santamaria sshd\[5258\]: Invalid user ubnt from 83.9.214.45
Apr 16 07:04:19 santamaria sshd\[5258\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.9.214.45
Apr 16 07:04:21 santamaria sshd\[5258\]: Failed password for invalid user ubnt from 83.9.214.45 port 41209 ssh2
...
2020-04-16 13:07:54
35.220.210.160 attack
Invalid user news from 35.220.210.160 port 51238
2020-04-16 12:57:09
82.118.236.186 attack
SSH login attempts.
2020-04-16 12:58:37
36.92.174.133 attackspam
Apr 16 06:58:28 server sshd[10384]: Failed password for invalid user mauro from 36.92.174.133 port 56804 ssh2
Apr 16 07:03:45 server sshd[14600]: Failed password for invalid user ubuntu from 36.92.174.133 port 58556 ssh2
Apr 16 07:08:58 server sshd[18514]: Failed password for invalid user dealer from 36.92.174.133 port 60308 ssh2
2020-04-16 13:10:31
62.210.219.124 attackbots
Apr 16 06:48:00 ift sshd\[48107\]: Failed password for invalid user admin from 62.210.219.124 port 47716 ssh2Apr 16 06:51:47 ift sshd\[48642\]: Invalid user ubuntu from 62.210.219.124Apr 16 06:51:49 ift sshd\[48642\]: Failed password for invalid user ubuntu from 62.210.219.124 port 41116 ssh2Apr 16 06:55:37 ift sshd\[49368\]: Invalid user idemo_user from 62.210.219.124Apr 16 06:55:39 ift sshd\[49368\]: Failed password for invalid user idemo_user from 62.210.219.124 port 35906 ssh2
...
2020-04-16 12:51:45
69.94.131.36 attackbots
Apr 16 05:44:10 web01.agentur-b-2.de postfix/smtpd[466370]: NOQUEUE: reject: RCPT from unknown[69.94.131.36]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo=
Apr 16 05:44:10 web01.agentur-b-2.de postfix/smtpd[464873]: NOQUEUE: reject: RCPT from unknown[69.94.131.36]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo=
Apr 16 05:44:10 web01.agentur-b-2.de postfix/smtpd[463880]: NOQUEUE: reject: RCPT from unknown[69.94.131.36]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo=
Apr 16 05:44:10 web01.agentur-b-2.de postfix/smtpd[461978]: NOQUEUE: reject: RCPT from unknown[69.94.131.36]: 450 4.7.1 
2020-04-16 12:44:18
14.116.188.151 attackbots
Apr 16 07:12:21 pkdns2 sshd\[15018\]: Invalid user user from 14.116.188.151Apr 16 07:12:23 pkdns2 sshd\[15018\]: Failed password for invalid user user from 14.116.188.151 port 41716 ssh2Apr 16 07:16:38 pkdns2 sshd\[15197\]: Invalid user django from 14.116.188.151Apr 16 07:16:40 pkdns2 sshd\[15197\]: Failed password for invalid user django from 14.116.188.151 port 35495 ssh2Apr 16 07:20:58 pkdns2 sshd\[15398\]: Invalid user ftpuser from 14.116.188.151Apr 16 07:20:59 pkdns2 sshd\[15398\]: Failed password for invalid user ftpuser from 14.116.188.151 port 57499 ssh2
...
2020-04-16 12:57:29
45.142.195.2 attack
2020-04-16 07:43:00 dovecot_login authenticator failed for \(User\) \[45.142.195.2\]: 535 Incorrect authentication data \(set_id=ready@org.ua\)2020-04-16 07:43:50 dovecot_login authenticator failed for \(User\) \[45.142.195.2\]: 535 Incorrect authentication data \(set_id=refunds@org.ua\)2020-04-16 07:44:40 dovecot_login authenticator failed for \(User\) \[45.142.195.2\]: 535 Incorrect authentication data \(set_id=remix@org.ua\)
...
2020-04-16 12:45:04
42.236.10.112 attackspambots
Web bot scraping website [bot:360Spider]
2020-04-16 12:36:53
14.140.218.214 attackspambots
Apr 16 05:52:00 srv01 sshd[23491]: Invalid user lynch from 14.140.218.214 port 37518
Apr 16 05:52:00 srv01 sshd[23491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.140.218.214
Apr 16 05:52:00 srv01 sshd[23491]: Invalid user lynch from 14.140.218.214 port 37518
Apr 16 05:52:02 srv01 sshd[23491]: Failed password for invalid user lynch from 14.140.218.214 port 37518 ssh2
Apr 16 05:55:49 srv01 sshd[23729]: Invalid user user from 14.140.218.214 port 40018
...
2020-04-16 12:45:48
222.186.175.151 attack
Apr 16 06:49:23 MainVPS sshd[28488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.151  user=root
Apr 16 06:49:25 MainVPS sshd[28488]: Failed password for root from 222.186.175.151 port 34062 ssh2
Apr 16 06:49:28 MainVPS sshd[28488]: Failed password for root from 222.186.175.151 port 34062 ssh2
Apr 16 06:49:23 MainVPS sshd[28488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.151  user=root
Apr 16 06:49:25 MainVPS sshd[28488]: Failed password for root from 222.186.175.151 port 34062 ssh2
Apr 16 06:49:28 MainVPS sshd[28488]: Failed password for root from 222.186.175.151 port 34062 ssh2
Apr 16 06:49:23 MainVPS sshd[28488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.151  user=root
Apr 16 06:49:25 MainVPS sshd[28488]: Failed password for root from 222.186.175.151 port 34062 ssh2
Apr 16 06:49:28 MainVPS sshd[28488]: Failed password for root from 222.18
2020-04-16 12:53:12
85.105.201.63 attackbots
Automatic report - Port Scan Attack
2020-04-16 12:56:37
128.199.150.228 attackbots
Apr 16 05:51:55 minden010 sshd[28265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.150.228
Apr 16 05:51:56 minden010 sshd[28265]: Failed password for invalid user albert from 128.199.150.228 port 59642 ssh2
Apr 16 05:55:53 minden010 sshd[29527]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.150.228
...
2020-04-16 12:34:03
101.36.179.159 attackspambots
Apr 16 05:47:49 h1745522 sshd[29041]: Invalid user sinusbot from 101.36.179.159 port 56896
Apr 16 05:47:49 h1745522 sshd[29041]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.36.179.159
Apr 16 05:47:49 h1745522 sshd[29041]: Invalid user sinusbot from 101.36.179.159 port 56896
Apr 16 05:47:50 h1745522 sshd[29041]: Failed password for invalid user sinusbot from 101.36.179.159 port 56896 ssh2
Apr 16 05:51:36 h1745522 sshd[29145]: Invalid user user from 101.36.179.159 port 46518
Apr 16 05:51:36 h1745522 sshd[29145]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.36.179.159
Apr 16 05:51:36 h1745522 sshd[29145]: Invalid user user from 101.36.179.159 port 46518
Apr 16 05:51:38 h1745522 sshd[29145]: Failed password for invalid user user from 101.36.179.159 port 46518 ssh2
Apr 16 05:55:27 h1745522 sshd[29265]: Invalid user lth from 101.36.179.159 port 36140
...
2020-04-16 13:02:13
114.5.245.153 attackbotsspam
20/4/15@23:55:55: FAIL: Alarm-Network address from=114.5.245.153
20/4/15@23:55:56: FAIL: Alarm-Network address from=114.5.245.153
...
2020-04-16 12:32:46

最近上报的IP列表

10.13.254.44 2606:4700:10::6816:4571 2606:4700:10::6816:3578 2606:4700:10::6814:7731
2606:4700:10::ac43:2157 2606:4700:10::ac43:1677 2606:4700:10::6816:1275 2606:4700:10::ac43:2733
110.78.138.146 2606:4700:10::ac43:2354 2606:4700:10::ac43:1598 2606:4700:10::6814:7235
2606:4700:10::6816:3842 2606:4700:10::6814:7820 2606:4700:10::6814:8726 103.129.197.233
10.0.219.72 64.191.149.77 2606:4700:10::6816:398d 2606:4700:10::ac43:901