Mail Gönderme Problemi

Category	Test name	Information send feedback
Parent	Domain NS records	Nameserver records returned by the parent servers are: ns1.betopan.com.tr. ['176.40.123.149'] [TTL=43200] ns2.betopan.com.tr. ['176.40.123.149'] [TTL=43200] tr.cctld.authdns.ripe.net directed me to ns1.nic.tr which was kind enough to give us that information. NOTE: You also need to know that you have a country code second-level domain (ccSLD) that may require an extra NS lookup and may delay a little the visitors to your website!
	TLD Parent Check	WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing.
	Your nameservers are listed	Good. The parent server tr.cctld.authdns.ripe.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
	DNS Parent sent Glue	Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
	Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS	NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: ns1.betopan.com.tr ['176.40.123.149'] [TTL=3600] ns2.betopan.com.tr ['176.40.123.149'] [TTL=3600]
	Recursive Queries	I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are: 176.40.123.149
	Same Glue	The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
	Glue for NS records	OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
	Mismatched NS records	OK. The NS records at all your nameservers are identical.
	DNS servers responded	Good. All nameservers listed at the parent server responded.
	Name of nameservers are valid	OK. All of the NS records that your nameservers report seem valid.
	Multiple Nameservers	Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
	Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
	Missing nameservers reported by parent	OK. All NS records are the same at the parent and at your nameservers.
	Missing nameservers reported by your nameservers	OK. All nameservers returned by the parent server tr.cctld.authdns.ripe.net are the same as the ones reported by your nameservers.
	Domain CNAMEs	OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
	NSs CNAME check	OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
	Different subnets	WARNING: Not all of your nameservers are in different subnets
	IPs of nameservers are public	Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
	DNS servers allow TCP connection	OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
	Different autonomous systems	WARNING: Single point of failure
	Stealth NS records sent	Ok. No stealth ns records are sent
SOA	SOA record	The SOA record is: Primary nameserver: ns1.betopan.com.tr Hostmaster E-mail address: hostmaster.betopan.com.tr Serial #: 19 Refresh: 900 Retry: 600 Expire: 86400 1 days Default TTL: 3600
	NSs have same SOA serial	OK. All your nameservers agree that your SOA serial number is 19.
	SOA MNAME entry	OK. ns1.betopan.com.tr That server is listed at the parent servers.
	SOA Serial	Your SOA serial number is: 19. The recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made. That seems to be 1969/12/31 18:0:19
	SOA REFRESH	WARNING: Your SOA REFRESH interval is: 900. That is not so ok
	SOA RETRY	Your SOA RETRY value is: 600. Looks ok
	SOA EXPIRE	Your SOA EXPIRE number is: 86400. That is NOT OK
	SOA MINIMUM TTL	Your SOA MINIMUM TTL is: 3600. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 3600 is OK.
MX	MX Records	Your MX records that were reported by your nameservers are: 10 betopan.com.tr 176.40.123.149 [These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
	Different MX records at nameservers	Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
	MX name validity	Good. I did not detect any invalid hostnames for your MX records.
	MX IPs are public	OK. All of your MX records appear to use public IPs.
	MX CNAME Check	OK. No problems here.
	MX A request returns CNAME	OK. No CNAMEs returned for A records lookups.
	MX is not IP	OK. All of your MX records are host names.
	Number of MX records	OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
	Mismatched MX A	OK. I did not detect differing IPs for your MX records.
	Duplicate MX A records	OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
	Reverse MX A records (PTR)	Your reverse (PTR) record: 149.123.40.176.in-addr.arpa -> betopan.com.tr You have reverse (PTR) records for all your IPs, that is a good thing.
WWW	WWW A Record	Your www.betopan.com.tr A record is: www.betopan.com.tr [176.40.123.149]
	IPs are public	OK. All of your WWW IPs appear to be public IPs.
	WWW CNAME	OK. No CNAME sanırım onlarda da problem görünmüyor paylaşmak için test sonuçlarını da sizinle paylaşıyorum

Forum

Mail Gönderme Problemi

Microsoft Teams Toplantıları İçin 10 İpucu

Windows 10 Üzerinde Kali Linux Kullanımı

Bir Samsung Modeli Daha Android 14 Güncellemesi Aldı. İşte Tüm Modeller!

Acı Kaybımız, Uğur Demir’ i Kaybettik

Bir Veritabanı Sunucusuna Brute Force ile Saldırmak ve Sunucuyu Savunmak

Windows 0x0000011b Ağ Yazdırma Hatası Nasıl Düzeltilir