SShortSingh.
Back to feed

Developer Launches TTMAIL, a Serverless Disposable Email Service Built on Cloudflare

0
·1 views

A developer has built TTMAIL, a lightweight temporary email platform designed as a faster, ad-free alternative to existing disposable mail services. The service runs on Next.js 15 and Cloudflare's edge infrastructure, including Cloudflare Pages, Workers, and D1 serverless SQLite database. Users can instantly generate a temporary inbox without signing up, choose from four domains, and optionally set a custom alias with password for multi-device recovery. TTMAIL also offers a REST API with JSON endpoints, making it suitable for automated testing workflows using tools like Cypress or Playwright. The platform is live at trytempmail.co and includes interactive API documentation.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How to Revoke Stolen AWS IAM Credentials in Real Time During an S3 Attack

When an EC2 instance is compromised, attackers can extract temporary IAM credentials from the metadata service and begin bulk-downloading sensitive S3 data before a patch is ready. AWS GuardDuty can detect this via an Exfiltration:S3/AnomalousBehavior alert, triggering an urgent need to cut off access immediately. The fastest containment method is attaching an inline deny policy to the compromised IAM role using a timestamp condition, which invalidates all credentials issued before that moment — with no propagation delay. This approach blocks the attacker's stolen credentials across any network, while allowing the EC2 instance to automatically fetch new, valid credentials from the metadata service. Simply isolating the instance via a security group change is insufficient, as the attacker may already hold the credentials off-instance.

0
ProgrammingDEV Community ·

Aspiring Data Engineer Documents First Week of Tools and Environment Setup

A newcomer to data engineering has shared their experience from their first week of learning the field. They focused on setting up a development environment and understanding how Git Bash integrates with GitHub for version control. The learner also practiced uploading and managing projects on GitHub and explored DBeaver as a database management tool. Looking ahead, they plan to expand their knowledge across databases, data pipelines, cloud technologies, and other core data engineering tools.

0
ProgrammingDEV Community ·

A Mislabelled EPSG Code in a Dropdown Could Place Belgrade in Rajasthan

A developer discovered a critical coordinate system bug while documenting a mobile mapping ingestion system that processes LiDAR road surveys. The upload form offered two EPSG codes labelled as the same Gauss-Krüger zone 7 projection, but one — EPSG:8686 — was actually Slovenia's national grid, offset by six degrees of longitude. Applying the wrong code to Belgrade coordinates produced a location in Rajasthan, India, roughly 5,400 kilometres off. No survey data had been processed using the erroneous option, so no records were corrupted. The correct modern EPSG code for Gauss-Krüger zone 7 in the Balkans region is 3909, and the error stemmed from a gap in a numeric series that made a nearby, plausible-looking code easy to mistake for the right one.

0
ProgrammingDEV Community ·

Step-by-Step Git Workflow: From File Creation to GitHub Push

A basic Git workflow begins on your local machine by creating a project folder and files using terminal commands like mkdir and touch. Once files are ready, Git is initialized with git init, and files are moved to the staging area using git add before being committed to the local repository with git commit. The local repository serves as a hidden, Git-managed storage space on your computer. To sync with GitHub, a remote connection is established using git remote add origin followed by the repository's HTTPS link. Finally, git push origin main uploads the committed files from the local machine to the remote GitHub repository.