Turkey (Türkçe)
Germany (German)
Worldwide (English)
A Records
IPv4 addresses used by the domain.
Halkalı merkez mahallesi fatih cd ozgur apt no 46 , Küçükçekmece , İstanbul , 34303 , TR
Review A, MX, NS and TXT records of a domain from one organized screen.
IPv4 addresses used by the domain.
| Hostname | Type | IP Address | TTL |
|---|
Mail servers receiving email for the domain.
| Hostname | Type | Priority | Target | TTL |
|---|
Authoritative name servers for the domain.
| Hostname | Type | Target | TTL |
|---|
Verification, SPF, DKIM and other text values.
| Hostname | Type | Value | TTL |
|---|
Each record type controls a different part of domain resolution, email delivery and verification.
IPv4 addresses used by the domain.
Mail servers receiving email for the domain.
Authoritative name servers for the domain.
Verification, SPF, DKIM and other text values.
DNS directly affects website access, email delivery, security validation and service continuity.
A and CNAME records direct visitors to the correct web infrastructure.
MX, SPF, DKIM and DMARC records help messages reach the correct mail system.
TXT records are used for ownership verification and email authentication policies.
Stable authoritative name servers reduce resolution failures and connection delays.
After a DNS change, cached records may continue to be used until their TTL expires.
An incorrect IPv4 address can direct visitors to the wrong server or make the site unreachable.
If registrar and DNS provider name servers do not match, records may not resolve.
Missing or conflicting SPF, DKIM and DMARC records can cause delivery problems.
Results reflect the records returned during the query. Recursive resolvers may temporarily return older values depending on TTL and propagation status.
DNS converts human-readable domain names into IP addresses and other service records used by internet applications.
Propagation depends on TTL, resolver cache and provider settings. Some changes appear within minutes, while others may take up to 24 or 48 hours.
TTL indicates how long a DNS resolver may cache a record before requesting it again.
Different networks may use different cached DNS data. Local DNS cache, ISP resolvers and propagation timing can cause temporary differences.