Domain > api2.kfs.clp-staging.jp

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2018-10-11	13.33.165.41 (ClassC)
2020-07-31	99.84.248.42 (ClassC)
2020-07-31	13.249.135.63 (ClassC)
2020-07-31	99.84.248.109 (ClassC)
2020-07-31	99.84.248.27 (ClassC)
2025-01-05	99.84.66.51 (ClassC)
2025-01-21	99.84.66.53 (ClassC)
2025-04-11	99.84.66.70 (ClassC)

HTTP/1.1 403 ForbiddenServer: CloudFrontDate: Sat, 29 Jun 2024 18:34:37 GMTContent-Type: text/htmlContent-Length: 915Connection: keep-aliveX-Cache: Error from cloudfrontVia: 1.1 98e601970ea59f4d5f56a7

!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: gCP9DPu4_i2pW47v47f2sPwzVVJr3_XPYwcTYeYdBqVVJGTDiTEpOQ/PRE>ADDRESS>/ADDRESS>/BODY>/HTML>

Subdomains

Date	Domain	IP
cms.admin02.kfs.clp-staging.jp	2024-08-01	18.238.238.57
api2.kfs.clp-staging.jp	2025-01-05	99.84.66.51
dev3.kfs.clp-staging.jp	2024-08-25	99.84.66.41
cms.admin.kfs.clp-staging.jp	2024-07-19	18.161.6.85

View on OTX | View on ThreatMiner

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

Domain > api2.kfs.clp-staging.jp

Is this malicious?

DNS Resolutions

Port 80

Subdomains