Report for 234565789566082.xyz
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (
z.nic.xyz.).
Domain NS records:
-
ns1.turkticaret.net. TTL=3600
[NO GLUE4]
[NO GLUE6]
-
ns2.turkticaret.net. TTL=3600
[NO GLUE4]
[NO GLUE6]
-
ns3.turkticaret.net. TTL=3600
[NO GLUE4]
[NO GLUE6]
Test ignored, name servers are located outside of current zone.
Name Servers Have A Records
OK.
Found A records for all name servers.
- ns1.turkticaret.net. → 31.186.17.251
- ns2.turkticaret.net. → 188.40.172.123
- ns3.turkticaret.net. → 31.186.17.253
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
NOTICE:
While reading domain NS records at parent name servers,
we found name servers without AAAA records.
- ns1.turkticaret.net. → ?
- ns2.turkticaret.net. → ?
- ns3.turkticaret.net. → ?
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Could not get NS records from your name servers.
Domain SOA Record:
- Primary nameserver: ns1.turkticaret.net.
- Hostmaster (e-mail): nsadmin.234565789566082.xyz.
- Serial: 1
- Refresh: 10800
- Retry: 3600
- Expire: 604800
- Minimum TTL: 3600
Name Servers Agreement on Serial Number
OK.
All name servers (3) have the same
serial number [1].
Having different serials on your name servers may show inconsistencies between name servers
configuration (multiple masters), or communication errors (ACL and firewall issues).
NOTICE:
Although your serial is valid [1],
it's not using recommended serial number format YYYYMMDDnn,
where YYYY is four-digit year number, MM is the month,
DD is the day and nn is the sequence number in case zone
file is updated more than once per day.
OK.
Primary name server is ns1.turkticaret.net. and is listed at the parent name servers.
The MNAME field defines the Primary Master name server for the zone,
this name server should be found in your NS records.
OK.
Contact email for DNS problems is
[email protected]. (
nsadmin.234565789566082.xyz.).
RNAME field defines an administrative email for your zone. RFC2142 recommends using
hostmaster
e-mail for this purpose, but any valid e-mail address can be used.
OK.
Refresh interval is 10800.
Recommended values [1200 .. 43200] (20 min ... 12 hours).
Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.
OK.
Retry interval is 3600.
Recommended values [120 .. 7200] (2 minutes .. 2 hours).
Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.
OK.
Expire interval is 604800.
Recommended values [604800 .. 1209600] (1 week ... 2 weeks).
Expiry defines zone expiration time in seconds after which slave must re-validate zone file,
if contacting master fails then slave will stop responding to any queries.
OK.
Minimum TTL value is 3600.
Recommended values [3600 .. 86400] (1 hour ... 1 day).
Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves
to cache negative responses.
Could not get MX records from your name servers.
Could not get MX records from your name servers.
OK.
Domain
234565789566082.xyz. resolves to:
Domain Name IPs are Public
OK.
No private IPs found for 234565789566082.xyz..
Web servers using private IPs can't be reached from the Internet.
OK.
Domain
www.234565789566082.xyz. resolves to:
OK.
No private IPs found for www.234565789566082.xyz..
Web servers using private IPs can't be reached from the Internet.
Report completed in 1.01 seconds.
Recent reports:
hotmail.com
citi.com
stc
gojek.com
freedsl.tv