Domain tools · Free
Check any domain’s records as the world sees them, and from inside Syria
Your national .sy domain or a global one: we ask 21 points in 16 cities, including Damascus and Aleppo, and compare every answer with what its authoritative name servers say.
The domain’s name servers
Propagation
—
Different value
—
No answer
—
Average response time
—
Every answer
Where the record has arrived, and where it’s waiting
Each point on the map is a city we asked, and the table starts with the problems: a different value still in a resolver’s cache, or a point that didn’t answer in time.
Public resolvers
If one of them sees your old value, ask it to flush its cache so it asks your servers again.
Response time
How long each point waited for its resolver’s answer in this check, from fastest to slowest.
Each point’s time appears after the check.
| Point | Answer | TTL | Time | Status |
|---|---|---|---|---|
| Damascus Syria, Illevante agent | — | — | — | Checking |
| Aleppo Syria, Illevante agent | — | — | — | Checking |
| Dubai UAE | — | — | — | Checking |
| Riyadh Saudi Arabia | — | — | — | Checking |
| Cairo Egypt | — | — | — | Checking |
| Istanbul Türkiye | — | — | — | Checking |
| Frankfurt Germany | — | — | — | Checking |
| Amsterdam Netherlands | — | — | — | Checking |
| London United Kingdom | — | — | — | Checking |
| Virginia United States | — | — | — | Checking |
| São Paulo Brazil | — | — | — | Checking |
| Johannesburg South Africa | — | — | — | Checking |
| Mumbai India | — | — | — | Checking |
| Singapore Singapore | — | — | — | Checking |
| Tokyo Japan | — | — | — | Checking |
| Sydney Australia | — | — | — | Checking |
| Cloudflare Public resolver | — | — | — | Checking |
| Google Public resolver | — | — | — | Checking |
| Quad9 Public resolver | — | — | — | Checking |
| OpenDNS Public resolver | — | — | — | Checking |
| AdGuard Public resolver | — | — | — | Checking |
From inside Syria
What your site’s visitors in Damascus and Aleppo see
Global propagation tools have no check point in Syria. Illevante’s agents in Damascus and Aleppo ask the local network’s resolver just as your visitor does, so you see its own answer, not a faraway city’s.
DamascusChecking
—Local network resolver—
AleppoChecking
—Local network resolver—
Answer path
From the root to your domain’s servers, step by step
We follow the query the way any resolver asks it: from the root servers to the extension’s servers, then to your domain’s name servers. If a server is slow or doesn’t answer from a given network, you see it here by name.
The path appears after the check.
Domain health
A report that says what’s sound, what needs fixing, and how
With every check we review the name servers, the zone, email and DNSSEC, and write a ready-to-copy fix line for each note.
Result
The report appears after you check a domain.
- Name server matchDoes the extension delegate to the same servers your zone announces?
- Server responseDoes every name server answer over UDP and TCP?
- Open queriesDo your servers answer for domains other than yours?
- Serial numberDo all the servers hold the same version of the zone?
- Network diversityAre the servers spread over more than one network?
- Mail destinationDoes every MX record have an address mail can reach?
- SPF recordDoes the domain say who sends mail in its name?
- DMARC policyDoes the domain stop mail that spoofs its name?
- CAA recordDoes the domain say who issues its certificates?
- DNSSEC signingIs signing enabled and validated from the extension?
When will the change arrive?
The delay has a deadline: what’s left of the TTL
A resolver that asked before your change keeps the old answer until its time runs out, then asks your servers again. We read what’s left at each resolver, so we can tell you when propagation completes instead of “wait 48 hours”.
Enter a domain and choose a record type, then press “Check”.
Watch until it completes
We re-check every 5 minutes while the page is open, for up to 48 hours, and let you know here when every resolver matches your value.
Alerts by email, Telegram and WhatsApp Coming soon
What the tool checks
Twelve record types
Plus advanced checks Coming soon
HTTPSSVCBTLSASSHFPNAPTRNSEC3PARAM
An IP address becomes a PTR query
Type the address on its own, and we look up its name in in-addr.arpa or ip6.arpa.
Arabic names
Type مثال.سورية as is, and we convert it to its technical form and check it.
Expected value
Type what you’re expecting, and we compare every answer with it.
Export and share
CSV that reads Arabic correctly in Excel, JSON, a result link, and a PDF report.
After the check
FAQ5 questions
Questions about the DNS checker
Didn’t find your answer? Our technical support team is with you around the clock.
Contact supportWe compare every answer with what your domain’s authoritative name servers say, or with the value you enter. “Matches” means the resolver sees the same record, and “Different value” means it’s still holding an old answer until its time runs out.
Because a resolver keeps every answer for the TTL written in the record, and doesn’t ask again until it runs out. We read what’s left at each resolver, so you know when propagation will complete.
Yes: national .sy domains and all their extensions, exactly like global domains, plus two check points inside Syria, in Damascus and Aleppo, that see what your visitors there see.
Because the .sy extension itself isn’t signed yet, so its domains can’t be signed. The tool mentions this and doesn’t count it as a fault in your domain.
Export it as CSV or JSON, copy the share link, or print a PDF report with the Illevante logo and the Domain Management Department’s details.
Your domain’s records, as the world sees them and as Syria sees them
Check any national or global domain for free, and fix whatever shows up in DNS Console.
- Check points in every query
- 21
- Inside Syria, in Damascus and Aleppo
- 2
- Record types
- 12