# Amazon Route 53 A highly available, scalable AWS DNS web service for domain registration, DNS routing, and health checking. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Behind the console: An AiTM phishing kit harvesting AWS console credentials and beyond DevFeed: [Behind the console: An AiTM phishing kit harvesting AWS console credentials and beyond]() Original publisher: [Read original article]() Author: Datadog Published: 2026-06-24T00:00:00Z Content type: article Language: en Sources: [Datadog Security Labs]() Topics: [Adversary-in-the-middle (AiTM)](), [Amazon Web Services](), [Security](), [MFA](), [Cloudflare](), [JavaScript](), [VirusTotal](), [Batch file](), [cURL](), [Amazon Route 53]() Tags: [adversary-in-the-middle-aitm](), [aws](), [batch](), [cloudflare](), [dns](), [javascript](), [mfa](), [security](), [virustotal]() ### AI overview Datadog Security Research analyzes a June 2026 campaign using cloned AWS console login pages and adversary-in-the-middle techniques to harvest credentials and MFA codes. The article details the phishing infrastructure, delivery methods, VirusTotal artifact, and JavaScript-based credential-harvesting flow. ### Source excerpt Datadog Security Research investigates a June 2026 adversary-in-the-middle phishing campaign that cloned the AWS console login page to harvest victim credentials and multi-factor authentication codes. ## Developer and security research roundup: DNS resilience, RIPE NCC token exposure, IPv6 measurement, and quantum cryptography DevFeed: [Developer and security research roundup: DNS resilience, RIPE NCC token exposure, IPv6 measurement, and quantum cryptography]() Original publisher: [Read original article]() Author: Russ Published: 2026-06-19T12:04:04Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [Amazon Route 53](), [Resilience](), [Network](), [Security, Privacy and Abuse Prevention](), [Quantum Computing](), [Cryptography](), [Internet]() Tags: [cryptography](), [dns](), [ipv6](), [network](), [public-key](), [quantum](), [resilience](), [rsa](), [worth-reading]() ### AI overview A roundup of developer and security research covering authoritative DNS resilience, exposed RIPE NCC single sign-on session tokens, IPv6 address measurement, asset speculation, and progress toward quantum computers breaking RSA-based public-key cryptography. ### Source excerpt In this post, I discuss our recent work that models and analyses the resilience of authoritative DNS infrastructure that supports individual domain names on the Internet. The RIPE NCC made its all-powerful single sign-on tokens available to over 1000 third parties. From a single link click, any logged-in RIPE NCC user would leak their session token. Identifying active IPv6 addresses is a challenging task, but it's also an important one. As researchers and network operators, it helps us understand the current deployment, identify weak spots that need strengthening, and detect vulnerable devices for disclosure. The fundamental bubble barometer is that speculators buy an asset because they expect the price to keep rising, not because they want the income generated by the asset. Indeed, most speculators don't plan on holding the asset long enough receive any income. Recently, there has been a surge in progress in quantum computing that has shortened the hypothetical timeline on which quantum computers can 'break' traditional public-key cryptography that uses the RSA scheme. ## Backdoored node-ipc npm releases steal developer credentials through DNS queries DevFeed: [Backdoored node-ipc npm releases steal developer credentials through DNS queries]() Original publisher: [Read original article]() Author: Nick Frichette Published: 2026-05-14T00:00:00Z Content type: article Language: en Sources: [Datadog Security Labs]() Topics: [Malware](), [npm](), [backdoor](), [payload](), [Amazon Route 53](), [Code](), [Cloud](), [Kubernetes](), [Databases](), [OpenSSH]() Tags: [analysis](), [backdoor](), [cloud](), [code](), [database](), [developer](), [dns](), [fork](), [kubernetes](), [malware](), [npm](), [payload](), [process](), [ssh]() ### AI overview This article analyzes three backdoored node-ipc releases published to npm on May 14, 2026. The malicious CommonJS entrypoint launches a detached process, collects environment, host, developer, cloud, package manager, source control, Kubernetes, database, and SSH credentials, archives the data, and attempts DNS TXT exfiltration. ### Source excerpt An analysis of backdoored node-ipc npm releases that add an obfuscated credential collection and DNS exfiltration payload to the CommonJS entrypoint. ## Branch-Based Deployments with Private Staging on Cloudflare DevFeed: [Branch-Based Deployments with Private Staging on Cloudflare]() Original publisher: [Read original article]() Author: EduuhMuraya Published: 2026-01-14T00:00:00Z Content type: tutorial Language: en Sources: [EduuhMuraya]() Topics: [Cloudflare](), [Cloudflare Access](), [Deployment](), [Authentication](), [GitHub Actions](), [Zero Trust](), [Amazon Route 53](), [API](), [hosting](), [OAuth]() Tags: [api](), [authentication](), [cloudflare](), [cloudflare-access](), [deployment](), [dns](), [github](), [github-actions](), [hosting](), [my-blog](), [oauth](), [self-hosted](), [zero-trust]() ### AI overview A practical guide to deploying a blog's production and private staging environments with Cloudflare Pages, protecting staging with Cloudflare Access and email OTP authentication, and automating deployments through GitHub Actions. ### Source excerpt How I use Cloudflare Pages for deployments and Cloudflare Access to protect my staging environment with email OTP authentication. ## Automating Cloudflare Pages with the API DevFeed: [Automating Cloudflare Pages with the API]() Original publisher: [Read original article]() Author: EduuhMuraya Published: 2026-01-11T00:00:00Z Content type: tutorial Language: en Sources: [EduuhMuraya]() Topics: [Cloudflare](), [API](), [cURL](), [Amazon Route 53]() Tags: [api](), [apis](), [cloudflare](), [dns](), [how-to](), [my-blog]() ### AI overview A practical guide to automating Cloudflare Pages with its API and cURL. It explains how to configure staging and production domains to serve different branches, manage API credentials, and set up DNS records without using the dashboard. ### Source excerpt The Cloudflare Pages dashboard is fine but I'd rather just curl things. Here's how I set up staging and production branches pointing to different domains without touching the UI. ## Using SSL in HatchBox with AWS Route 53 DevFeed: [Using SSL in HatchBox with AWS Route 53]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-06-23T07:01:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Amazon Route 53](), [Rails](), [SSL](), [Amazon Web Services](), [AWS IAM](), [Deployment](), [JSON]() Tags: [aws](), [cartazzi](), [credentials](), [deployment](), [hatchbox](), [iam](), [json](), [rails](), [route53](), [ssl]() ### AI overview A practical guide to configuring wildcard SSL in HatchBox with AWS Route 53. It explains the required Route 53 setup, IAM user and JSON policy configuration, credential handling, and the addition of route53:ListResourceRecordSets after an incomplete policy caused validation problems. ### Source excerpt HatchBox continues to be my favorite tool for Rails deployment hands down. And this includes Dockarno - my own Bash based Docker deployment tool. When something you pay for replaces something you wrote yourself, that's a sign of its very, very strong goodness. I just used HatchBox to support SSL wildcard deployment for something I'm building and the process was a tad bit tricky so I thought I'd write it up. HatchBox has excellent built in SSL support using Let's Encrypt but when you use wildcard SSL, you get asked for the Route 53 Key and the Route 53 secret. Here's how you get those: On AWS, in Route 53 In Route 53, make sure you have *.domain.extension defined to allow it to be wildcard. On AWS, in IAM In the IAM console, you need to: Add a user Add that user to a group Add a JSON policy document Here is the JSON policy that you need to add: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "route53:GetChange", "Resource": "arn:aws:route53:::change/*" }, { "Effect": "Allow", "Action": "route53:ChangeResourceRecordSets", "Resource": "arn:aws:route53:::hostedzone/*" }, { "Effect": "Allow", "Action": "route53:ListHostedZonesByName", "Resource": "*" }, { "Effect": "Allow", "Action": "route53:ListHostedZones", "Resource": "*" }, { "Effect": "Allow", "Action": "route53:ListResourceRecordSets", "Resource": "*" } ] } After you've added that user then you will be prompted with the normal AWS access key / secret key. Save the credentials and then add them to HatchBox. HatchBox will then got thru an API session with AWS and validate the key. My Experience and Chris's Brilliant Work I started from documentation I found online (see below) that turned out to be incomplete. When I examined the HatchBox log for the transaction, I saw this: -----> Connecting to SOMETHING3-lb (138.68.227.244 port 22) as root Uploaded /etc/logrotate.d/acme.sh Executing 'curl https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh | sh -s -- --install-online' % ## Heroku and Route 53 - Using Amazon for Domain Registration with Heroku for Hosting DevFeed: [Heroku and Route 53 - Using Amazon for Domain Registration with Heroku for Hosting]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-12-29T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Heroku](), [Amazon Route 53](), [amazon](), [hosting]() Tags: [amazon](), [dns](), [domain](), [heroku](), [hosting](), [route]() ### AI overview A blog article documents adding the domains okrsnow.com and www.okrsnow.com to a Heroku application and configuring DNS providers with the resulting Heroku DNS targets. ### Source excerpt https://devcenter.heroku.com/articles/route-53 https://devcenter.heroku.com/articles/route-53 okrsnow on  master [🏎💨] via ⬢ v12.8.1 via 💎 v2.6.5 on ☁ us-west-2 took 5m33s ❯ heroku domains:add okrsnow.com Adding okrsnow.com to ⬢ okrsnow... done Configure your app's DNS provider to point to the DNS Target thawing-coral-9zbepdxpaa0ondgs6ubrpre7.herokudns.com. For help, see https://devcenter.heroku.com/articles/custom-domains The domain okrsnow.com has been enqueued for addition Run heroku domains:wait 'okrsnow.com' to wait for completion okrsnow on  master [🏎💨] via ⬢ v12.8.1 via 💎 v2.6.5 on ☁ us-west-2 took 2s ❯ heroku domains:add www.okrsnow.com Adding www.okrsnow.com to ⬢ okrsnow... done Configure your app's DNS provider to point to the DNS Target quiet-cephalopod-d3uo5fkp1t6x7dnqtpyc1jue.herokudns.com. For help, see https://devcenter.heroku.com/articles/custom-domains The domain www.okrsnow.com has been enqueued for addition Run heroku domains:wait 'www.okrsnow.com' to wait for completion okrsnow on  master [🏎💨] via ⬢ v12.8.1 via 💎 v2.6.5 on ☁ us-west-2 ❯ ## Wildcard LetsEncrypt Certificates on Forge DevFeed: [Wildcard LetsEncrypt Certificates on Forge]() Original publisher: [Read original article]() Author: Taylor Otwell Published: 2018-03-16T16:41:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Amazon Route 53](), [Cloudflare](), [Digital Ocean](), [PHP](), [API](), [MySQL](), [Redis]() Tags: [aws](), [cloudflare](), [digitalocean](), [dns](), [laravel](), [mysql](), [php](), [redis]() ### AI overview Laravel Forge now supports wildcard Let's Encrypt certificates with automatic renewal. Issuing these certificates requires the DNS-01 challenge and API credentials for a supported DNS provider: AWS Route 53, Cloudflare, or DigitalOcean. ### Source excerpt Today we're happy to announce support for wildcard LetsEncrypt certificates on Laravel Forge. Of course, like other certificates, these certificates will automatically be renewed by Forge.