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: Cape Coral

Region: Florida

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:       71.208.0.0 - 71.223.255.255
CIDR:           71.208.0.0/12
NetName:        CENTURYLINK-LEGACY-QWEST-INET-118
NetHandle:      NET-71-208-0-0-1
Parent:         NET71 (NET-71-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   CenturyLink Communications, LLC (CCL-534)
RegDate:        2005-05-06
Updated:        2018-10-04
Ref:            https://rdap.arin.net/registry/ip/71.208.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


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


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

;; QUESTION SECTION:
;71.215.0.124.			IN	A

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

;; Query time: 3 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 03 19:56:54 CST 2026
;; MSG SIZE  rcvd: 105
Host info
124.0.215.71.in-addr.arpa domain name pointer 71-215-0-124.ftmy.centurylink.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
124.0.215.71.in-addr.arpa	name = 71-215-0-124.ftmy.centurylink.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
123.212.48.26 attackbots
Automatic report - Banned IP Access
2019-12-19 23:28:14
106.13.113.204 attackbotsspam
Dec 19 16:16:46 MK-Soft-VM7 sshd[24606]: Failed password for root from 106.13.113.204 port 50088 ssh2
...
2019-12-19 23:28:56
45.117.182.79 attackbotsspam
Brute force SMTP login attempts.
2019-12-19 23:07:38
159.203.59.38 attackbots
Dec 19 15:34:28 tux-35-217 sshd\[16231\]: Invalid user www from 159.203.59.38 port 55934
Dec 19 15:34:28 tux-35-217 sshd\[16231\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.59.38
Dec 19 15:34:29 tux-35-217 sshd\[16231\]: Failed password for invalid user www from 159.203.59.38 port 55934 ssh2
Dec 19 15:39:28 tux-35-217 sshd\[16282\]: Invalid user admin from 159.203.59.38 port 60706
Dec 19 15:39:28 tux-35-217 sshd\[16282\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.59.38
...
2019-12-19 22:59:37
183.82.96.58 attackbotsspam
Dec 19 05:13:01 auw2 sshd\[21634\]: Invalid user test from 183.82.96.58
Dec 19 05:13:01 auw2 sshd\[21634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.96.58
Dec 19 05:13:03 auw2 sshd\[21634\]: Failed password for invalid user test from 183.82.96.58 port 54489 ssh2
Dec 19 05:19:37 auw2 sshd\[22261\]: Invalid user operator from 183.82.96.58
Dec 19 05:19:37 auw2 sshd\[22261\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.96.58
2019-12-19 23:24:21
185.176.27.6 attackspambots
Dec 19 15:26:57 h2177944 kernel: \[9640582.550970\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.6 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=40961 PROTO=TCP SPT=58822 DPT=64066 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 19 15:57:17 h2177944 kernel: \[9642402.332047\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.6 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=57809 PROTO=TCP SPT=58822 DPT=42801 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 19 16:02:31 h2177944 kernel: \[9642716.484054\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.6 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=47564 PROTO=TCP SPT=58822 DPT=5032 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 19 16:06:01 h2177944 kernel: \[9642926.607833\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.6 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=25346 PROTO=TCP SPT=58822 DPT=60787 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 19 16:07:44 h2177944 kernel: \[9643029.468955\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.176.27.6 DST=85.214.117.9 L
2019-12-19 23:13:38
49.235.83.156 attackspambots
Dec 19 15:18:00 sip sshd[16303]: Failed password for root from 49.235.83.156 port 45488 ssh2
Dec 19 15:38:58 sip sshd[16451]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.83.156
Dec 19 15:38:59 sip sshd[16451]: Failed password for invalid user wallop from 49.235.83.156 port 33938 ssh2
2019-12-19 23:21:24
149.202.251.94 attackbots
Brute force attack against VPN service
2019-12-19 22:54:19
180.215.120.2 attack
Dec 19 14:50:55 web8 sshd\[27877\]: Invalid user qqqqqqqq from 180.215.120.2
Dec 19 14:50:55 web8 sshd\[27877\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.215.120.2
Dec 19 14:50:57 web8 sshd\[27877\]: Failed password for invalid user qqqqqqqq from 180.215.120.2 port 38102 ssh2
Dec 19 14:56:41 web8 sshd\[30713\]: Invalid user password from 180.215.120.2
Dec 19 14:56:41 web8 sshd\[30713\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.215.120.2
2019-12-19 22:59:06
223.71.139.97 attackbots
Dec 19 15:55:22 legacy sshd[15334]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.71.139.97
Dec 19 15:55:24 legacy sshd[15334]: Failed password for invalid user fredvik from 223.71.139.97 port 51388 ssh2
Dec 19 16:03:00 legacy sshd[15631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.71.139.97
...
2019-12-19 23:08:00
190.2.118.244 attackbots
Dec 19 15:39:15 grey postfix/smtpd\[13130\]: NOQUEUE: reject: RCPT from unknown\[190.2.118.244\]: 554 5.7.1 Service unavailable\; Client host \[190.2.118.244\] blocked using bl.spamcop.net\; Blocked - see https://www.spamcop.net/bl.shtml\?190.2.118.244\; from=\ to=\ proto=ESMTP helo=\<244.118.2.190.ros.express.com.ar\>
...
2019-12-19 23:09:40
75.100.6.5 attackspambots
SSH Bruteforce attack
2019-12-19 23:02:27
101.96.113.50 attack
Dec 19 15:39:23 ArkNodeAT sshd\[1765\]: Invalid user mysql from 101.96.113.50
Dec 19 15:39:23 ArkNodeAT sshd\[1765\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.96.113.50
Dec 19 15:39:25 ArkNodeAT sshd\[1765\]: Failed password for invalid user mysql from 101.96.113.50 port 38658 ssh2
2019-12-19 23:02:05
165.227.69.39 attack
Dec 19 15:33:08 h2812830 sshd[10594]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.69.39  user=root
Dec 19 15:33:11 h2812830 sshd[10594]: Failed password for root from 165.227.69.39 port 37692 ssh2
Dec 19 15:41:26 h2812830 sshd[10693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.69.39  user=operator
Dec 19 15:41:29 h2812830 sshd[10693]: Failed password for operator from 165.227.69.39 port 55650 ssh2
Dec 19 15:46:44 h2812830 sshd[10786]: Invalid user saeterhaug from 165.227.69.39 port 57564
...
2019-12-19 22:58:34
138.197.89.212 attackspambots
Dec 19 04:50:23 web9 sshd\[9472\]: Invalid user atwater from 138.197.89.212
Dec 19 04:50:23 web9 sshd\[9472\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.89.212
Dec 19 04:50:25 web9 sshd\[9472\]: Failed password for invalid user atwater from 138.197.89.212 port 41710 ssh2
Dec 19 04:55:52 web9 sshd\[10259\]: Invalid user mal123 from 138.197.89.212
Dec 19 04:55:52 web9 sshd\[10259\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.89.212
2019-12-19 23:08:22

Recently Reported IPs

2606:4700:10::ac43:1003 58.246.155.87 91.227.114.170 150.228.149.164
190.4.202.166 101.36.106.75 110.78.158.234 183.207.48.139
27.78.166.86 110.77.248.15 2606:4700:10::6816:2092 2606:4700:10::6816:3832
2606:4700:10::6816:2988 3.250.151.208 156.226.174.212 61.221.79.64
237.21.144.152 119.103.150.19 2606:4700:10::6816:679 2606:4700:10::6816:4324