Domain > key2act.work

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2018-10-22	143.204.158.9 (ClassC)
2018-10-22	143.204.158.43 (ClassC)
2019-11-05	99.84.127.57 (ClassC)
2020-09-08	143.204.150.50 (ClassC)
2020-09-08	143.204.150.90 (ClassC)
2020-11-09	54.230.248.100 (ClassC)
2020-11-09	54.230.248.49 (ClassC)
2020-11-09	54.230.248.72 (ClassC)
2020-12-04	99.84.176.105 (ClassC)
2020-12-04	99.84.176.89 (ClassC)
2021-01-07	13.226.49.114 (ClassC)
2024-07-08	18.161.6.64 (ClassC)
2025-01-26	3.163.189.11 (ClassC)
2025-04-22	99.84.66.34 (ClassC)
2025-05-16	3.163.189.104 (ClassC)
2025-07-28	18.161.6.63 (ClassC)
2025-08-08	18.161.6.45 (ClassC)

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Sun, 10 Mar 2024 02:16:25 GMTContent-Type: text/htmlContent-Length: 915Connection: keep-aliveX-Cache: Error from cloudfrontVia: 1.1 ffc1e24c06bfbb135c0a4d

!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd>HTML>HEAD>META HTTP-EQUIVContent-Type CONTENTtext/html; charsetiso-8859-1>TITLE>ERROR: The request could not be satisfied/TITLE>/HEAD>BODY>H1>403 ERROR/H1>H2>The request could not be satisfied./H2>HR noshade size1px>Bad request.We cant connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.BR clearall>If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.BR clearall>HR noshade size1px>PRE>Generated by cloudfront (CloudFront)Request ID: Rtbi8mzhYxgI5Y5WUEitUj5bgKXRU0swrOjtcltBEIlIqp41e4CGpQ/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > key2act.work

Is this malicious?

DNS Resolutions

Port 80