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

Region: Arizona

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.
#


NetRange:       63.152.0.0 - 63.159.255.255
CIDR:           63.152.0.0/13
NetName:        CENTURYLINK-LEGACY-QWEST-INET-16
NetHandle:      NET-63-152-0-0-1
Parent:         NET63 (NET-63-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   CenturyLink Communications, LLC (CCL-534)
RegDate:        2000-07-12
Updated:        2018-02-21
Ref:            https://rdap.arin.net/registry/ip/63.152.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:        2026-04-22
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


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

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


#
# 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 <<>> 63.158.167.73
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2682
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;63.158.167.73.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Aug 26 22:16:03 CST 2026
;; MSG SIZE  rcvd: 106
Host info
b'73.167.158.63.in-addr.arpa domain name pointer 63-158-167-73.dia.static.centurylink.net.
'
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
73.167.158.63.in-addr.arpa	name = 63-158-167-73.dia.static.centurylink.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
130.61.72.90 attackbots
Oct 13 17:12:19 firewall sshd[25284]: Failed password for root from 130.61.72.90 port 42968 ssh2
Oct 13 17:16:08 firewall sshd[25376]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.61.72.90  user=root
Oct 13 17:16:09 firewall sshd[25376]: Failed password for root from 130.61.72.90 port 54168 ssh2
...
2019-10-14 04:55:20
168.255.251.126 attack
Feb 10 03:28:35 dillonfme sshd\[15426\]: Invalid user mb from 168.255.251.126 port 49392
Feb 10 03:28:35 dillonfme sshd\[15426\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.255.251.126
Feb 10 03:28:37 dillonfme sshd\[15426\]: Failed password for invalid user mb from 168.255.251.126 port 49392 ssh2
Feb 10 03:33:56 dillonfme sshd\[15589\]: Invalid user ftpuser from 168.255.251.126 port 40298
Feb 10 03:33:56 dillonfme sshd\[15589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.255.251.126
...
2019-10-14 04:32:53
122.115.230.183 attackbots
2019-10-14T03:16:49.696732enmeeting.mahidol.ac.th sshd\[1414\]: User root from 122.115.230.183 not allowed because not listed in AllowUsers
2019-10-14T03:16:49.821507enmeeting.mahidol.ac.th sshd\[1414\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.115.230.183  user=root
2019-10-14T03:16:51.780365enmeeting.mahidol.ac.th sshd\[1414\]: Failed password for invalid user root from 122.115.230.183 port 48806 ssh2
...
2019-10-14 04:19:37
159.89.155.148 attack
Oct 13 20:08:43 game-panel sshd[13263]: Failed password for root from 159.89.155.148 port 38224 ssh2
Oct 13 20:12:47 game-panel sshd[13509]: Failed password for root from 159.89.155.148 port 49432 ssh2
2019-10-14 04:25:55
89.151.179.175 attackspambots
Automatic report - Port Scan Attack
2019-10-14 04:23:26
91.74.234.154 attackspambots
Brute force SMTP login attempted.
...
2019-10-14 04:29:21
185.90.118.18 attack
10/13/2019-16:26:45.998342 185.90.118.18 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 04:32:39
168.232.8.8 attackspambots
Mar  8 13:40:00 dillonfme sshd\[16310\]: Invalid user git from 168.232.8.8 port 47710
Mar  8 13:40:00 dillonfme sshd\[16310\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.8.8
Mar  8 13:40:03 dillonfme sshd\[16310\]: Failed password for invalid user git from 168.232.8.8 port 47710 ssh2
Mar  8 13:46:39 dillonfme sshd\[16427\]: Invalid user testtest from 168.232.8.8 port 60244
Mar  8 13:46:39 dillonfme sshd\[16427\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.8.8
...
2019-10-14 04:36:09
2001:bc8:4400:2500::4:409 attackspam
[munged]::443 2001:bc8:4400:2500::4:409 - - [13/Oct/2019:22:16:35 +0200] "POST /[munged]: HTTP/1.1" 200 6737 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
[munged]::443 2001:bc8:4400:2500::4:409 - - [13/Oct/2019:22:16:37 +0200] "POST /[munged]: HTTP/1.1" 200 6599 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-14 04:33:53
103.60.126.80 attackbotsspam
2019-10-13T20:48:35.050086abusebot-5.cloudsearch.cf sshd\[11705\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.60.126.80  user=root
2019-10-14 04:51:38
168.227.99.10 attackspambots
Apr 16 14:43:36 yesfletchmain sshd\[9975\]: Invalid user loverd from 168.227.99.10 port 42994
Apr 16 14:43:36 yesfletchmain sshd\[9975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.227.99.10
Apr 16 14:43:38 yesfletchmain sshd\[9975\]: Failed password for invalid user loverd from 168.227.99.10 port 42994 ssh2
Apr 16 14:47:07 yesfletchmain sshd\[10247\]: Invalid user hong from 168.227.99.10 port 41580
Apr 16 14:47:07 yesfletchmain sshd\[10247\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.227.99.10
...
2019-10-14 04:43:42
222.186.173.142 attackspambots
Oct 13 22:47:10 fr01 sshd[29081]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142  user=root
Oct 13 22:47:12 fr01 sshd[29081]: Failed password for root from 222.186.173.142 port 48670 ssh2
...
2019-10-14 04:55:01
36.66.69.33 attackbots
Automatic report - Banned IP Access
2019-10-14 04:26:23
61.133.232.254 attackbots
2019-10-13T20:16:52.535956abusebot-5.cloudsearch.cf sshd\[11406\]: Invalid user alice from 61.133.232.254 port 4084
2019-10-14 04:19:54
168.181.51.146 attack
May 25 23:38:39 yesfletchmain sshd\[4760\]: Invalid user ian from 168.181.51.146 port 6280
May 25 23:38:39 yesfletchmain sshd\[4760\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.181.51.146
May 25 23:38:41 yesfletchmain sshd\[4760\]: Failed password for invalid user ian from 168.181.51.146 port 6280 ssh2
May 25 23:45:22 yesfletchmain sshd\[5009\]: Invalid user alainapi from 168.181.51.146 port 37753
May 25 23:45:22 yesfletchmain sshd\[5009\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.181.51.146
...
2019-10-14 04:54:03

Recently Reported IPs

39.144.124.157 60.5.26.155 60.27.226.38 58.17.113.22
42.236.216.105 44.4.92.191 39.154.11.8 34.96.60.219
223.91.88.87 223.73.27.77 123.5.21.198 120.82.83.234
120.82.68.64 120.230.26.107 120.230.23.237 120.219.68.72
120.216.108.215 115.48.113.24 43.112.192.136 42.111.31.82