Domain > assets.aumo.jp

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2019-07-03	99.86.58.27 (ClassC)
2019-07-31	13.225.190.84 (ClassC)
2019-07-31	13.225.190.125 (ClassC)
2019-07-31	13.225.190.15 (ClassC)
2019-12-18	99.84.181.56 (ClassC)
2019-12-18	99.84.181.6 (ClassC)
2019-12-18	99.84.181.110 (ClassC)
2020-05-18	13.227.47.16 (ClassC)
2020-05-18	13.227.47.31 (ClassC)
2020-05-18	13.227.47.61 (ClassC)
2020-05-18	13.227.47.96 (ClassC)
2025-01-29	108.138.94.10 (ClassC)
2025-03-30	18.161.6.66 (ClassC)
2025-05-18	108.138.94.35 (ClassC)
2025-08-05	18.161.6.80 (ClassC)
2025-09-16	3.169.173.81 (ClassC)
2026-03-01	3.169.173.50 (ClassC)

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Mon, 19 Feb 2024 02:08:12 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: ulJv-aacBdlodtSqQT7PTQDQye6G3rlxpqI-wiPos2w1r-t7BXbNXw/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

Port 443

View on OTX | View on ThreatMiner

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

Domain > assets.aumo.jp

Is this malicious?

DNS Resolutions

Port 80

Port 443