Table of Contents

Telenegar Mail Test Tool

The Telenegar Mail Test Tool measures how trustworthy a real e-mail looks to the receiving mail servers, and gives it a deliverability score out of 10. You get a temporary address, send an e-mail to it from the server, application or mailbox you want to test, and a report appears within seconds.

Unlike Mail Check, which reads a domain's DNS records without sending anything, Mail Test examines an e-mail that actually arrived. That lets it measure things that only exist on a real message: whether SPF passed for the server that really sent it, whether its DKIM signature verified, and how the sending server identifies itself.

It helps system administrators, developers and e-mail engineers find out why mail lands in the spam folder, and confirm that a new mail server, newsletter service or application is set up correctly before it goes live.


How to Perform a Mail Test

# **Sign in.** The tool uses credits, so an account is required.
# **Create the address.** Click **Create test address**. A temporary address such as ''t-d4gr5ing-tniu25-tonuwmh3ov@mailtest.telenegar.ir'' is shown. It is valid for **60 minutes** and accepts **one message**.
# **Send an e-mail to it.** Use the server, application or mailbox you want to test, with a realistic subject and text. Very short or empty messages are judged more harshly than real mail.
# **Keep the page open.** When the message arrives the report is shown automatically. If you reload the page while the address is still valid, the test continues.

<note important> Send the test from the same path your real e-mail takes (your application, your newsletter service, your company mail server). If you send it from a personal mailbox such as Gmail, the result describes Gmail's servers, not yours. </note>


What Is Checked

The score is out of 10 and is split between the checks like this:

Check Points What it looks at
SPF 2 Whether the sending server is authorized by the SPF record of the sender domain.
DKIM 2 Whether the message carries a valid DKIM signature, whether the signing domain matches the From address, and how long the key is.
DMARC 1.5 Whether the From domain publishes a DMARC policy and whether SPF or DKIM aligns with it. A policy of p=none earns 1 point; quarantine or reject earns the full 1.5.
Blacklists (RBL) 1.5 Whether the sending IP is listed on public spam blacklists.
Reverse DNS (PTR) 1 Whether the sending IP has a PTR record whose name resolves back to the same IP.
HELO name 0.5 Whether the name the server announces is a real domain name that resolves to its IP.
TLS encryption 0.5 Whether the message was delivered encrypted, with TLS 1.2 or newer.
Message headers 0.5 Whether From, Date, Message-ID and Subject are present and valid.
Message content 0.5 Spam-filter red flags: HTML without a plain-text part, links to bare IP addresses or URL shorteners, link text that shows a different domain than the link target, risky attachment types, subjects in capitals.

Reading the score

Score Verdict Meaning
8.5 - 10 Excellent Well configured; no important problem found.
6.5 - 8.4 Good Mostly fine, with a few things worth improving.
4 - 6.4 Fair Problems that may send mail to the spam folder.
below 4 Poor Serious problems; much of the mail will be treated as spam or rejected.

Every check that is not a full pass explains the problem and suggests a fix.

"Not checked"

Sometimes a check cannot be made, for example because of a temporary DNS problem, or because one blacklist does not answer our server. Such a check is shown as Not checked and is left out of the score instead of counting against you. For blacklists, the result states which lists were actually asked; the verdict “not listed” only covers those.


Cost and Privacy


Key Use Cases & Diagnostics

1. Why does my e-mail go to spam?

Run a test from the exact system that sends the problem mail. The report shows whether SPF, DKIM and DMARC pass for that real message, which is usually where the cause is. See Email Deliverability Guide.

2. Checking a new mail server

Before sending to customers, verify that the server has a correct PTR record, a HELO name that matches its IP, working TLS, and that its IP is not on a blacklist.

3. Checking a newsletter or transactional e-mail service

Confirm that the service signs with your domain (a valid DKIM signature that matches the From domain) rather than its own, otherwise DMARC will not count it.

4. Verifying a fix

After changing DNS records, send a new test. Each test uses a new address, so results are never mixed with earlier ones.