AliasMail가입 필요 없음10-Minute Auto 자폭제로 로그 및 제로 추적100% 영원히 무료인스턴트 별칭 생성개인정보 우선 아키텍처안전한 HTML 렌더링사용자 정의 사용자 이름 처리전세계 접속AliasMail가입 필요 없음10-Minute Auto 자폭제로 로그 및 제로 추적100% 영원히 무료인스턴트 별칭 생성개인정보 우선 아키텍처안전한 HTML 렌더링사용자 정의 사용자 이름 처리전세계 접속
📱 소셜 미디어

Masked Outbound Webhooks.Hide origin IP & sign payloads with HMAC-SHA256.

Stream incoming emails to user-configured webhook endpoints through Cloudflare Edge Relay. Conceal backend server IP address, protect against SSRF, and verify payload authenticity.

📬 즉시 수신함 열기📂 사이트맵
가이드 기사

3-Layer IP Masking & Cloudflare Edge Relay Architecture

Direct outbound webhooks from backend servers expose origin IP addresses in destination server logs, leaving cloud infrastructure vulnerable to tracing and targeted attacks. AliasMail uses a 3-Layer Edge Relay architecture powered by Cloudflare Workers to proxy outbound webhook requests.

HMAC-SHA256 Payload Signature Verification

Destination servers only log Cloudflare edge IP addresses (104.28.x.x / 2400:cb00::), completely concealing backend NestJS server IPs, hosting providers, and internal topology.

SSRF Protection & Subnet Security Guards

Every webhook dispatch includes an HMAC-SHA256 signature header (X-AliasMail-Signature) computed using Web Crypto API. Recipients can verify signature authenticity using their custom secret key while receiving sub-50ms real-time email payloads.

범주

📱 소셜 미디어

태그

#masked webhook delivery#outbound webhook ip masking#hmac sha256 signing#cloudflare edge relay#ssrf protection
자주 묻는 질문

알아야 할 모든 것

임시 이메일, 전달 별칭 및 로그 미저장 아키텍처에 대해 알아야 할 모든 것.

01How does masked webhook delivery hide my origin IP?
Outbound webhook requests are routed through a Cloudflare Worker relay. The destination server sees Cloudflare edge IPs, keeping your backend server IP completely hidden.
02How do I verify the HMAC-SHA256 signature in my code?
Calculate HMAC-SHA256 of the raw request body using your secret key and compare it with the X-AliasMail-Signature header.
03Are internal subnets protected against SSRF?
Yes. The relay inspects destination URLs and blocks requests targeting localhost (127.0.0.1) and private RFC 1918 subnets (10.0.0.0/8, 192.168.0.0/16).