Email domain
takas.lt email servers, SPF and DMARC
Mail for @takas.lt goes to mail2.takas.lt (MX priority 30), as DNS showed on 5 November 2026. The host sits under takas.lt. The domain publishes an SPF record ending in -all and a DMARC policy of p=none, which decide whether mail claiming to be from @takas.lt is trusted.
Check one address
Five checks a minute, no account needed. Nothing is sent to the address — we ask its mail server whether the mailbox exists, then disconnect.
Checking a whole list? The first 100 addresses are free, with results to download. No card.
By continuing you agree to our Terms and Privacy Policy.
takas.lt mail DNS on 5 November 2026
| Priority | MX host | Platform |
|---|---|---|
| 30 | mail2.takas.lt | Not identified |
| SPF | v=spf1 ip4:212.59.0.7/32 ip4:212.59.31.119/32 ip4:212.59.31.87/32 ip4:212.59.31.115/32 ip4:195.12.167.68/32 ip4:195.12.167.69/32 ip4:195.12.167.70/32 ip4:212.59.31.76/32 ip4:212.59.31.84/32 ip4:212.59.31.85/32 ip4:212.59.31.91/32 ip4:212.59.31.94/32 -all |
|---|---|
| DMARC | v=DMARC1; p=none; rua=mailto:[email protected] |
| MTA-STS | None published |
| TLS reporting | None published |
Read on 5 November 2026 with dig against 1.1.1.1 (8.8.8.8 as fallback); nothing sent to the mail servers. Check the records today with the email provider lookup.
takas.lt MX records
takas.lt publishes a single MX host, mail2.takas.lt. With no backup host, a sender that can't reach it queues the message and retries until the server answers or the queue gives up.
takas.lt SPF record
The record on 5 November 2026 was v=spf1 ip4:212.59.0.7/32 ip4:212.59.31.119/32 ip4:212.59.31.87/32 ip4:212.59.31.115/32 ip4:195.12.167.68/32 ip4:195.12.167.69/32 ip4:195.12.167.70/32 ip4:212.59.31.76/32 ip4:212.59.31.84/32 ip4:212.59.31.85/32 ip4:212.59.31.91/32 ip4:212.59.31.94/32 -all.
In plain terms, lists 12 IP ranges directly. The top level uses 0 DNS-querying terms; SPF allows 10 in total including nested includes (RFC 7208 §4.6.4).
It ends in a hard fail (-all): receivers may reject mail from any server the record does not list.
takas.lt DMARC policy
The record is v=DMARC1; p=none; rua=mailto:[email protected].
p=none only asks for reports; failing mail is delivered as normal.
Aggregate reports go to report.telia.net, so the domain's owner sees who sends mail as @takas.lt.
Can you verify @takas.lt addresses?
Our checker treats @takas.lt like any domain: syntax, MX, disposable and role checks first, then a made-up address to rule out a catch-all, then your address at RCPT TO, disconnecting without sending. We have not published a test of how mail2.takas.lt answers for @takas.lt, so we make no claim here about whether single mailboxes can be confirmed; each result carries its own reason.
Cleaning a list with these addresses
DNS tells you where mail goes, not whether one person's mailbox still exists. For a list, run the whole file through a verifier before you send: invalid rows come out, risky rows (catch-all, unknown, refused) go in their own segment, and valid rows are safe to mail.
Common questions
- What are the MX records for takas.lt?
- On 5 November 2026:
mail2.takas.lt(priority 30). - Does takas.lt have SPF and DMARC?
- On 5 November 2026
takas.ltpublished an SPF record ending in-alland a DMARC policy ofp=none. - Is takas.lt a disposable email domain?
- No.
takas.ltis not on the disposable domain list our checker uses, so @takas.lt addresses are checked like any other mailbox. See the disposable domain checker for the list.
Free checks for @takas.lt lists
- Bulk email checker for a pasted list or CSV
- Verify a whole file with a reason for every row
- SPF lookup counter
- MTA-STS checker
- Disposable email checker
Another domain? See every email domain we have mapped and what our checker does at each mailbox provider.
Got a list with @takas.lt addresses?
Sign in with Google and the first 100 addresses are checked free: valid, risky and invalid, with the reason for each row and a file to download. No card. After that, plans start at $9/mo for 2,500 emails a month.
By continuing you agree to our Terms and Privacy Policy.