Domain > markentier.space

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2020-12-08	99.86.100.60 (ClassC)
2020-12-08	99.86.100.129 (ClassC)
2024-06-26	204.246.191.42 (ClassC)
2024-07-19	204.246.191.95 (ClassC)
2025-08-27	13.224.14.60 (ClassC)

HTTP/1.1 200 OKContent-Type: text/htmlContent-Length: 1404Connection: keep-aliveDate: Wed, 26 Jun 2024 06:27:05 GMTLast-Modified: Tue, 17 Nov 2020 15:04:31 GMTETag: e8ebf9d0c1760facf84dd0eecd8f4c09x-a

!DOCTYPE html>html langen>head>  meta charsetUTF-8>  meta nameviewport contentwidthdevice-width, initial-scale1.0>  title>markentier.space index/title>  style>    html, body {      margin: 0;      padding: 0;      border: 0;      font-size: 24px;    }    body {      padding: 2rem 24%;    }  /style>/head>body>  h1>markentier.space index/h1>  hr/>  p>This website was created and deployed with terraform on AWS (CloudFront + S3)./p>  pre stylewhite-space: pre-wrap;>A Lambda@Edge function gathers the request/response data, publishes them via the closest regional SNS. This should reduce the latency as much as possible. (Previous attempt was to talk to S3 directly, but that would hurt far away edge locations.)A single region SQS is then subscribed to all those cross-region SNS topics, and triggers yet another (regular) Lambda function to process the messages. This SNS->SQS bridge is very light-weight, not much to configure or to set up.Finally the payload can then be stored in whatever data store we like (S3, RDS, ElastiCache, Keyspaces, DocumentDB, or even something external).Even if message processing takes significant amount of time, this is now decoupled from the edge request-response life cycle.Look forward to my TED talk and see me soon at an AMA of your favourite social media platform. ;-)  /pre>/body>/html>

View on OTX | View on ThreatMiner

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

Domain > markentier.space

Is this malicious?

DNS Resolutions

Port 80

Port 443