Nov 16, 2026 · 11 min read
Daum Mail Read Receipts: Does Daum Track Your Email?
A Daum Mail read receipt, called 수신확인 (read confirmation), is a transparent image hidden in the message, and Daum marks the mail as read when it loads. It works on Gmail addresses, nobody asks the recipient, and public receipt samples spell out the sender, the message and the recipient in plain text.
A recruiter in Seoul writes to you from a hanmail.net address. You open the message in Gmail, and in their 수신확인함 (read confirmation box) your line flips from 읽지않음 (unread) to 읽음 (read). That is Daum Mail tracking at work, and like Naver's version, it never asks you anything. Daum Mail, the webmail that began as Hanmail, is one of South Korea's two big homegrown mailboxes. On November 16, 2026 we read Daum's Korean help pages, the privacy policies that cover it and Kakao's press releases, then sent test requests to the receipt servers. We did not open a Daum account, so anything visible only after login is marked unverified.
Key Takeaways
- Daum's help center says every Daum Mail read receipt is a transparent image attached to the message, and that loading the image is what marks the mail as read.
- Daum keeps read confirmation records for 3 months, a twelfth of the 3 years its rival Naver keeps them.
- Two public receipt addresses, from 2019 and 2020, carry the sender's address, a message ID and the recipient's address in the URL path, and on November 16, 2026 both Daum and Kakao receipt servers still answered that format with a 43 byte, 1x1 transparent GIF.
- Daum's help center admits that opening a bounced message flips its status from 전송실패 (send failed) to 읽음 (read), which shows the receipt records an image load rather than a person reading.
- EasyPrivacy, AdGuard's Mail Tracking Protection filter and Ugly Email's tracker list had no rule for the Daum or Kakao receipt address on November 16, 2026, while Gblock's blocklist covers both receipt paths.
How Does a Daum Mail Read Receipt Work?
A Daum Mail read receipt is a tracking pixel. Daum says so in its help article on why a recipient who read the mail still shows as unread:
메일 발송 시 내용 안에 상대방의 수신을 확인하는 기능을 하는 이미지가 첨부되어 발송 (이미지는 투명하여 보이지 않음)
In English: when the mail is sent, an image that confirms the other person's receipt is attached inside the content, and the image is transparent, so it cannot be seen. The same sentence goes on to say that when the recipient reads the mail, the image is called along with it, and that is how Daum confirms the message was read.
The sender checks the result from a 수신확인 button to the right of the sent folder. Daum's mobile app help page says the app has the same box, where the sender can see whether each recipient has read the message or not.
None of this is new, and none of it was ever limited to Daum users. A 2002 press release from Daum Communications, which called Hanmail 국내 최초의 무료 웹메일 서비스 (Korea's first free webmail service), announced an upgraded 수신확인 feature that lets senders check whether mail sent to 외부 주소 (outside addresses) had been read. Gmail is an outside address.
What Does the Receipt Address Reveal?
In the public samples we found, the receipt address names who sent the mail, which message it was and who it went to. One turns up in the public source files of a Korean civic group's website, in a 2019 post apparently pasted from an email with the invisible image intact. Its address followed this pattern (we replaced the real addresses with placeholders):
https://confirm.mail.daum.net/confirmapi/v1/users/sender%40hanmail.net/cmails/20190504172634.9-…%40sender.hanmail.net/recipients/recipient%40naver.com
Left to right: the sender's hanmail.net address, a message ID opening with a timestamp (May 4, 2019, 17:26:34), and a recipient at naver.com. A test file in an open source mail project from 2020 shows the same structure on Kakao's server, confirm.mail.kakao.com, with /v1/users/, /cmails/ and /recipients/ segments.
On November 16, 2026 we sent one request in that format, with made up addresses, to each server. Both answered with an HTTP 302 redirect to a file called trans.gif on Daum's image server, t1.daumcdn.net, which turned out to be a 43 byte GIF measuring 1x1 pixel. The format still works. We have not seen a receipt inside a message sent in 2026, so whether today's receipts still carry addresses in readable form stays unverified.
This matters for Gmail users in a specific way. Google's image help page says that because Gmail fetches images through its own servers, "Senders can’t use image loading to get information about your computer or location." That hides your IP address. It does not hide your identity when the image address itself names you, and a receipt built like the samples above does exactly that.
What Does the Sender See, and for How Long?
The sender sees whether each recipient has read the message, and keeps that history for three months. Daum's article on how long read confirmation data is kept says records are kept for 3 months unless the member deletes them, and then disappear automatically. For scheduled mail, the three months start on the day the message actually goes out.
That is the friendliest number in this story. Our Naver Mail read receipt review found that Naver keeps the same kind of record for three years. Put side by side, a read time you hand a Naver sender today stays visible until November 2029; the same read time on Daum is gone by mid February 2027.
Two features ride on top of the receipt:
- Push alerts. Daum's help page on turning off read confirmation alerts describes a 수신 확인 알림 사용 (use read confirmation alerts) switch in the Android and iOS apps, which means a sender can get a phone notification about your read. Whether it starts on or off, Daum does not say.
- Unsend, but not for you. Daum's send cancellation article says '발송취소' 기능은 Daum 메일 계정으로 보낸 메일에서만 작동하는 기능입니다 (the send cancellation feature only works on mail sent to Daum mail accounts). Mail sent to Gmail can be tracked but never recalled.
When Does a Daum Read Receipt Get It Wrong?
A Daum receipt is wrong whenever the image and the reader part ways, and Daum lists the cases itself. The same help article gives five reasons a message can show as unread:
- The recipient has not opened it.
- The recipient's side uses a firewall.
- The recipient's mail is set to 받은 메일 이미지 안 보기 (don't show images in received mail).
- The recipient read it in Outlook or on a smartphone.
- The recipient sits on a hardened network, such as some companies, public offices and government agencies.
The error runs the other way too. Daum's article on bounced mail marked as read says: "반송 메일 열람 시 '수신확인'에서 '전송실패'가 '읽음'으로 전환됩니다." (When a bounced mail is opened, the status in 수신확인 changes from send failed to read.) The likely reason is that the bounce notice carries the original message, image included, so the sender opening it triggers a read that never happened.
Most coverage treats a read time as a fact about the recipient. Daum's own help center shows it is a fact about an image: anything that loads it counts as you, and anything that blocks it makes you invisible.
Is Daum Mail the Same as Kakao Mail?
They are two mailboxes that share a design, an account and, as far as we can see, a receipt system. A June 2023 Kakao press release announced a unified design for Daum Mail and Kakao Mail, and a switcher so that someone using both with one Kakao account can jump between the two inboxes. Daum's help page on that switcher still describes it: click the address at the top of the side menu to see your Daum Mail and Kakao Mail addresses. Kakao's receipt server, confirm.mail.kakao.com, answered our test request exactly like Daum's, redirecting to the same trans.gif.
Ownership has shifted around them. The Korea Times reported that Daum completed its split from Kakao on December 1, 2025, and that a new company, AXZ, now manages core services such as email. AXZ later renamed itself 주식회사 다음 (Daum Corp.), and that is the company named in Daum's current privacy policy, in force since July 27, 2026.
Does Daum Mail Protect Its Own Users From Trackers?
Partly, and mostly undocumented. The receipt article confirms that a Daum user can set their mailbox to not show images in received mail, but no current help page we found says where that setting lives or whether it starts on or off.
There is a hint about image proxies. Daum's article on images showing as broken boxes says images sent from plain http addresses break in Chrome and Edge because the browser blocks mixed content, and tells users to ask the sender to use https. A mailbox that fetched every remote image through its own https proxy, as Gmail does, would not hit that problem, so our inference is that Daum Mail sometimes loads images straight from the sender's server, exposing the reader's IP address. Daum does not say. We found nothing about stripping tracking parameters from links.
The privacy policies are silent on pixels. Daum's policy lists device information, IP address, cookies and service usage records as data collected automatically, and its section on automatic collection devices covers cookies only. Kakao's privacy policy, in force since October 28, 2026, is built the same way. Neither one mentions web beacons, tracking images or the read confirmation feature, even though Daum's help center calls the receipt an image.
Why Email Users Should Care
Read tracking usually means newsletters. Daum puts it in an ordinary personal mailbox, so the person watching is whoever wrote to you: a landlord, a former partner, a contact deciding when to follow up. They see your address and a status, and in the app they can get a ping.
Gmail's defaults do not stop it. Google's image settings page says "By default, when you get an email with an image, you’ll see the image automatically," and concedes that "Sometimes, senders may know whether you've opened an email that has an image." A Daum receipt is that case. Standard receipts under RFC 8098 ask the recipient's program for a notice it can refuse; as our explainer on how Gmail read receipts work notes, personal Gmail never sends them. A pixel needs no permission.
How Do You Block a Daum Mail Read Receipt in Gmail?
Stop the image from loading and the receipt stays on unread. Daum's failure list doubles as a list of defenses. In Gmail on a desktop browser:
- Turn off automatic images. In Gmail settings, scroll to Images and choose "Ask before displaying external images," as Google's image help page describes. A Daum receipt then stays dark unless you allow images for that message.
- Check the raw message. Open the three dot menu, choose "Show original," and search for confirm.mail.daum.net or confirm.mail.kakao.com. A match means the message carries a receipt. Our guide to detecting tracking pixels in Gmail walks through this view.
- Use a blocker that knows the Daum path. We read the Gblock extension's source: its blocklist has an entry for Kakao Corp covering confirm.mail.kakao.com/v1/users and confirm.mail.daum.net/confirmapi/v1/users, and has carried it since August 2024. Gblock blocks known spy pixels in Gmail on desktop Chrome, Edge, Brave and Arc, using a blocklist that updates automatically. It does not work in the Gmail mobile apps or in other mail programs.
- Set the same rule on your phone. The Gmail apps have the same ask before showing images option under Images.
- If you send from Daum yourself, Daum documents no way to leave the receipt out of a message. Its article on messages missing from read confirmation lists the exclusions: mail sent inside a Daum Cafe community, failed sends, and mail sent from an outside client such as Outlook over POP3 or IMAP.
For every method side by side, see our guide on how to block email tracking in Gmail.
Gblock Compared to Ugly Email, PixelBlock, Trocker, Proton Mail and HEY
Most tracker blockers run on lists, and lists built around Western marketing tools can miss Korean webmail. On November 16, 2026 we searched each tool's public list or source for daum, hanmail and kakao. Our email tracker Chrome extensions comparison covers the wider tradeoffs.
| Tool | Daum receipt rule | What else to know |
|---|---|---|
| Ugly Email | None in its live 57 line tracker list. | Blocks and flags pixels that match its list. |
| PixelBlock | None in its public code, last updated in 2015. | Also checks image width and height, so it may still catch a tiny receipt. |
| Trocker | None in its lists (source updated July 2026). | Also flags tiny unknown images, so it may still catch one. |
| Proton Mail | Not list dependent; tracking protection is on by default. | Proxies remote images; means moving your address out of Gmail. |
| HEY | Says it blocks spy trackers and names the sender. | A separate mail service at $99 a year after a 30 day trial. |
| Gblock | Yes, for both the Daum and Kakao receipt paths. | Keeps your Gmail address; desktop browsers only, not a phishing filter. |
The big public filter lists were no better. EasyPrivacy blocks Daum's and Kakao's web analytics hosts but not confirm.mail.daum.net, and AdGuard's Mail Tracking Protection filter (version 2.0.0.12, updated November 12, 2026) blocks Naver's receipt path but not Daum's or Kakao's. A missing rule is not proof a tool fails, since Trocker and PixelBlock also judge images by size. For a closer look at those three, read our Ugly Email, PixelBlock and Trocker alternatives comparison.
What We Could Not Verify
Without a Daum account, these points stay open; Daum's mail help center is the place to watch for changes:
- Whether receipts in mail sent in 2026 still put addresses in readable form, as the 2019 and 2020 samples did.
- Whether a sender can switch receipts off; Daum documents no such setting.
- Where the don't show images setting lives in Daum Mail and whether it is on by default.
- Whether the read confirmation alerts in the app start switched on.