Seznam.cz Email
seznam.cz · 2 records in Storage · JSON
Records 2
- caveatSeznam.cz (email-as-storage)
Storagefree tieridentity any-phone?card?evidence reportedstale on 2026-11-05
- caveatSeznam.cz Email — unlimited-size mailbox, message-count-bound
Storagefree tieridentity email?card?limit per-object-capevidence reportedstale on 2026-11-05
Seznam.cz (email-as-storage)
Storage- Free allowance
- Mailbox is byte-unlimited: 'Uživatel může schránku využívat v neomezené velikosti', with a 120,000-message cap that can be raised repeatedly
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- any-phone?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Mailbox is byte-unlimited: 'Uživatel může schránku využívat v neomezené velikosti', with a 120,000-message cap that can be raised repeatedly unit unlimited; metered on unstated |
|---|---|
| Price | none stated |
| Identity | any-phone (inferred, not read) not published |
| Egress | No metered egress; IMAP/POP access is included |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | sftp, rclone sftp |
| Tooling | IMAP (standard clients, rclone 'imap' style tooling via a mail-to-blob shim); no dedicated backend |
| Composes with | One mailbox x 120,000 messages x 35-50 MB per message is a multi-TB theoretical ceiling; identities are the limit |
| Reliability | message-count cap plus per-message size cap is the real ceiling; touchy about bulk IMAP |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | registrace.seznam.cz/ | 'Create a new e-mail address with Seznam. Or use your existing one: Gmail, Outlook, or another. / Create @seznam.cz address · Use my existing email · Use phone number' |
| 2026-10-21 | registrace.seznam.cz/ | phone flow: 'In the next step, you will verify your phone number by entering the SMS code'; raw HTML has three <input name="phone" maxlength="3"> prefix boxes plus a disabled suffix box |
| 2026-10-21 | registrace.seznam.cz/ | existing-email flow: 'To verify your email address, enter the verification code we sent to your email' |
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read
- Free allowance
- Docs page states verbatim: "Uživatel může schránku využívat v neomezené velikosti.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-capper-object-cap 35 MB
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Docs page states verbatim: "Uživatel může schránku využívat v neomezené velikosti. V praxi je každá schránka založena s limitem na 120 000 zpráv, který lze opakovaně navyšovat." = unlimited mailbox size; in practice each mailbox starts with a 120,000-message limit that can be raised repeatedly (on request). This is the only webmail found where the published limit is a MESSAGE COUNT, not a byte quota. unit unlimited; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
per-object-cap 35 MB attach send from web (25 MB from mobile app), 50 MB receive per message — that is the real per-blob size. 120,000 messages/mailbox is the binding constraint (a pull-count-style ceiling on object count, raisable on request). Sending-rate limits exist but are explicitly unpublished: "Tyto limity nejsou veřejné." |
| Identity | email (inferred, not read) not published |
| Egress | Unmetered by the provider — no transfer meter is published or charged; mail is delivered by SMTP/IMAP, not metered HTTP GET. No egress pricing exists for a mailbox. |
| Per-object cap | per-object-cap 35 MB (35000000 bytes) |
| Retention | not stated |
| Interface | rest, rclone rest |
| Tooling | Native IMAP, probe-verified live: imap.seznam.cz:993 -> * OK Seznam IMAP server ready / * CAPABILITY XLIST IMAP4rev1 AUTH=PLAIN AUTH=LOGIN AUTH=OAUTHBEARER AUTH=XOAUTH2 SASL-IR CHILDREN SORT I18NLEVEL=1 UIDPLUS ID MOVE UNSELECT. Any IMAP client or imapsync/offlineimap works. No rclone backend. |
| Composes with | Each account is byte-unlimited (message-count-bound), so a second account carries a second allowance. 120,000 messages × the 35 MB send cap = ~4.2 TB per account before the message-count ceiling even binds; raise the count via support and the ceiling moves. Free registration, no paid tier required. |
| Reliability | Operators state up front that they watch for excess use of the unlimited claim: rules are tuned to catch anyone probing "kde je ta skutečná hranice" (where the real boundary is). Message-count ceiling is enforced silently at fill time. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | o-seznam.cz/napoveda/email/mohlo-by-se-hodit/limity-schranky | "neomezené velikosti" + "120 000 zpráv" + 35/50 MB attach caps, read live 2026-10-21 |
| 2026-10-21 | source not published | probe: openssl s_client -connect imap.seznam.cz:993 -> * OK Seznam IMAP server ready + CAPABILITY incl. AUTH=PLAIN/OAUTHBEARER |
| 2026-10-21 | blog.seznam.cz/2008/12/spustili-jsme-neomezenou-velikost-ema | 2008 origin of the unlimited policy, incl. the anti-probing warning |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read