Report for turkiye.gov.tr

Report created on: Fri, 22 Nov 2024 16:51:45 GMT

Parent		100
NS		51
SOA		83
MX		100
Mail		100
Web		100

NS Records at Parent Servers

We have successfully fetched domain's NS records from parent name server (ns74.ns.tr.).
Domain NS records:

ns1.turkiye.gov.tr. TTL=43200 [94.55.117.7] [2a00:1d58:0:1901:94:55:117:7]
ns2.turkiye.gov.tr. TTL=43200 [94.55.118.8] [2a00:1d58:0:1901:94:55:118:8]

Missing Glue

OK. Parent name servers are offering glue for domain's name servers. We received name servers list and it's IP addresses from parent name server (ns74.ns.tr.).

Name Servers Have A Records

OK. Found A records for all name servers.

ns1.turkiye.gov.tr. → 94.55.117.7
ns2.turkiye.gov.tr. → 94.55.118.8

To reach your name servers via IPv4 an A record is needed for each name server.

Name Servers Have AAAA Records

OK. Found AAAA records for all name servers.

ns1.turkiye.gov.tr. → 2a00:1d58:0:1901:94:55:117:7
ns2.turkiye.gov.tr. → 2a00:1d58:0:1901:94:55:118:8

To reach your name servers via IPv6 an AAAA record is needed for each name server.

NS Records

Your name servers returned 2 NS records:

ns1.turkiye.gov.tr. TTL=43200 [94.55.117.7] [2a00:1d58:0:1901:94:55:117:7]
ns2.turkiye.gov.tr. TTL=43200 [94.55.118.8] [2a00:1d58:0:1901:94:55:118:8]

All Name Servers Responded

FAIL: While quering domain's records, some of your name servers didn't responded. Name servers which didn't responded:

udp4:94.55.118.8
udp6:2a00:1d58:0:1901:94:55:117:7

Glue Check

OK. No differences found. The glue provided by the parent name servers has to match the data provided by the authoritative name servers.

Allow Recursive Queries

WARNING: The following name servers announces themselves as open DNS servers:

udp6:2a00:1d58:0:1901:94:55:118:8

On all name servers which acts as caching name servers recursive queries should be restricted to local networks. Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks. Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic, email and other traffic to malicious hosts compromising security.

Check Name Servers Count

OK. Domain has 2 name servers. Recommended number, between 2 and 7 name servers (RFC 2182 recommends to have at least 3 authoritative name servers for domains).

Identical NS Records

OK. All your name servers reported identical NS records. Each name server should return identical NS records.

Check for Lame Name servers

OK. No lame name servers found. All of your name servers are configured to be either master or slave for your domain.

Check All IPs are Public

OK. No private IPs found. Name servers using private IPs can't be reached from the Internet causing DNS delays.

Name Servers Have A Records

OK. Found A records for each name servers.

ns1.turkiye.gov.tr. → 94.55.117.7
ns2.turkiye.gov.tr. → 94.55.118.8

To reach your name servers via IPv4 an A record is needed for each name server.

Name Servers Have AAAA Records

OK. Found AAAA records for all name servers.

ns1.turkiye.gov.tr. → 2a00:1d58:0:1901:94:55:117:7
ns2.turkiye.gov.tr. → 2a00:1d58:0:1901:94:55:118:8

To reach your name servers via IPv6 an AAAA record is needed for each name server.

Name Servers Have Valid Names

OK. All names are valid. Name server name should be a valid host name, no partial name or IP address.

Check for Stealth Name Servers

OK. No stealth name servers found. All name servers returned by domain name servers should be listed at parent servers.

Check for Missing Name Servers

OK. No missing name servers found. All name servers returned by the parent name servers should have an NS record at your name servers.

No CNAME in NS Records

OK. No CNAMEs found in NS records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA) and must not point to any CNAME records. RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record) it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with NS and MX records. Despite this restrictions, there are many working configuration using CNAME with NS and MX records.

Allow TCP connections

WARNING: Couldn't connect using TCP protocol:

tcp4:94.55.117.7
tcp4:94.55.118.8
tcp6:2a00:1d58:0:1901:94:55:117:7

Check your name server's configurations and firewall rules. When response to a DNS query exceeds 512 bytes, TCP is negotiated and used, all name servers should allow TCP connections (port 53).

Name Servers Distributed on Multiple Networks

OK. Name servers are dispersed on 2 different C class networks:

94.55.117.0/24:
- ns1.turkiye.gov.tr.
94.55.118.0/24:
- ns2.turkiye.gov.tr.

Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).

Name Servers Distributed on Multiple ASNs

WARNING: All name servers are located in one Autonomous System:

AS47524:
- ns1.turkiye.gov.tr.
- ns2.turkiye.gov.tr.

Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).

Name Servers Versions

OK. Name servers software versions are not exposed:

2a00:1d58:0:1901:94:55:117:7: "unknown"
2a00:1d58:0:1901:94:55:118:8: "BIND"
94.55.117.7: "BIND"
94.55.118.8: "unknown"

Exposing name server's versions may be risky, when a new vulnerability is found your name servers may be automatically exploited by script kiddies until you patch the system. Learn how to hide version.

Check SOA Record

Domain SOA Record:

Primary nameserver: turkiye.gov.tr.
Hostmaster (e-mail): dnsadmin.turkiye.gov.tr.
Serial: 2024112201
Refresh: 28800
Retry: 7200
Expire: 2419200
Minimum TTL: 10800

Name Servers Agreement on Serial Number

WARNING: We found different serial numbers on your name servers, it's OK if you had modified your zone recently.

2a00:1d58:0:1901:94:55:117:7: 2024112201
2a00:1d58:0:1901:94:55:118:8: 2024112201
94.55.117.7: 2024112201
94.55.118.8: 0

Having different serials on your name servers may show inconsistencies between name servers configuration (multiple masters), or communication errors (ACL and firewall issues).

SOA Number Format

OK. Serial number format OK [2024112201]. Your serial number is following general convention for serial number 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.

SOA Mname

WARNING: Primary name server turkiye.gov.tr. listed in SOA Record is not found 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.

SOA Rname

OK. Contact email for DNS problems is [email protected]. (dnsadmin.turkiye.gov.tr.). 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.

SOA Refresh

OK. Refresh interval is 28800. Recommended values [1200 .. 43200] (20 min ... 12 hours). Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.

SOA Retry

OK. Retry interval is 7200. 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.

SOA Expire

WARNING: Expire interval is 2419200. 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.

SOA Minimum TTL

OK. Minimum TTL value is 10800. 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.

MX Records

Your name servers returned 2 MX records:

10 mailgw2.turkiye.gov.tr. TTL=43200
10 mailgw1.turkiye.gov.tr. TTL=43200

Identical MX Records

OK. All name servers returned identical MX records.

Mail Servers Have A Records

OK. Found A records for all mail servers.

mailgw1.turkiye.gov.tr. → 94.55.120.163
mailgw2.turkiye.gov.tr. → 94.55.120.164

To reach your mail servers via IPv4 an A record is needed for each mail server.

Mail Servers Have AAAA Records

NOTICE: While reading domain NS records at parent mail servers, we found mail servers without AAAA records.

mailgw1.turkiye.gov.tr. → ?
mailgw2.turkiye.gov.tr. → ?

To reach your mail servers via IPv6 an AAAA record is needed for each mail server.

Reverse Entries for MX records

OK. All mail servers have reverse DNS entries configured correctly.

	Server	IP	PTR (Reverse)	IPs
	mailgw2.turkiye.gov.tr.	94.55.120.164	mailgw2.turkiye.gov.tr.	94.55.120.164
	mailgw1.turkiye.gov.tr.	94.55.120.163	mailgw1.turkiye.gov.tr.	94.55.120.163

All mail servers should have a reverse DNS (PTR) entry for each IP address (RFC 1912). Missing reverse DNS entries will make many mail servers to reject your e-mails or mark them as SPAM.

All IP's reverse DNS entries should resolve back to IP address (IP → PTR → IP). Many mail servers are configured to reject e-mails from IPs with inconsistent reverse DNS configuration.

Check MX Records for Invalid Chars

OK. No invalid characters found. Name field from MX records should be a valid host name.

Check MX Records IPs are Public

OK. No private IPs found. Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.

Check MX Records for Duplicates

OK. No MX records duplicates (same IP addresses) found. Although technically valid, duplicate MX records have no benefits and can cause confusion.

Only Host Names in MX Records

OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.

No CNAME in MX Records

OK. No CNAMEs found in MX records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA) and must not point to any CNAME records. RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record) it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with NS and MX records. Despite this restrictions, there are many working configuration using CNAME with NS and MX records.

RBL Check

OK. Mail servers IPs are not blacklisted.

Check Google Apps Settings

Test ignored, domain is not using Google Apps.

Connect to Mail Servers

Could not get MX records from your name servers.

Resolve Domain Name

OK. Domain turkiye.gov.tr. resolves to:

94.55.118.33

Domain Name IPs are Public

OK. No private IPs found for turkiye.gov.tr.. Web servers using private IPs can't be reached from the Internet.

Resolve WWW

OK. Domain www.turkiye.gov.tr. resolves to:

94.55.118.33

WWW IPs are Public

OK. No private IPs found for www.turkiye.gov.tr.. Web servers using private IPs can't be reached from the Internet.

Report completed in 18.67 seconds.

Recent reports: jordy.app presentemaine.org bnpparibas.dz caar.dz saa.dz