Hi,
The IP 71.19.252.244 has just been banned by Fail2Ban after
5 attempts against SSH.
Here is more information about 71.19.252.244:
[Querying whois.arin.net]
[whois.arin.net]
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# http://www.arin.net/public/whoisinaccuracy/index.xhtml
#
#
# Query terms are ambiguous. The query is assumed to be:
# "n 71.19.252.244"
#
# Use "?" to get help.
#
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=71.19.252.244?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2
#
NetRange: 71.19.240.0 - 71.19.255.255
CIDR: 71.19.240.0/20
NetName: ESD-SURREY-V4
NetHandle: NET-71-19-240-0-1
Parent: NET71 (NET-71-0-0-0-0)
NetType: Direct Allocation
OriginAS: AS11831
Organization: eSecureData (ESECU-4)
RegDate: 2011-07-21
Updated: 2013-07-25
Comment: Surrey Central City facility
Ref: http://whois.arin.net/rest/net/NET-71-19-240-0-1
OrgName: eSecureData
OrgId: ESECU-4
Address: 1478 Hartley Ave.
City: Coquitlam
StateProv: BC
PostalCode: V3K 7A1
Country: CA
RegDate: 2008-03-31
Updated: 2014-11-14
Ref: http://whois.arin.net/rest/org/ESECU-4
OrgAbuseHandle: SUPPO579-ARIN
OrgAbuseName: Support Department
OrgAbusePhone: +1-800-620-1985
OrgAbuseEmail: noc@esecuredata.com
OrgAbuseRef: http://whois.arin.net/rest/poc/SUPPO579-ARIN
OrgNOCHandle: SUPPO579-ARIN
OrgNOCName: Support Department
OrgNOCPhone: +1-800-620-1985
OrgNOCEmail: noc@esecuredata.com
OrgNOCRef: http://whois.arin.net/rest/poc/SUPPO579-ARIN
OrgTechHandle: SUPPO579-ARIN
OrgTechName: Support Department
OrgTechPhone: +1-800-620-1985
OrgTechEmail: noc@esecuredata.com
OrgTechRef: http://whois.arin.net/rest/poc/SUPPO579-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# http://www.arin.net/public/whoisinaccuracy/index.xhtml
#
Regards,
Fail2Ban
No comments:
Post a Comment