DNS Check Report

Category Status Test name Result
Parent done Domain NS records Nameserver records returned by the parent servers are:

noah.ns.cloudflare.com   ['108.162.193.133'] (NO GLUE)   [TTL=15 minutes]
novalee.ns.cloudflare.com   ['108.162.194.182'] (NO GLUE)   [TTL=15 minutes]

ns1.uniregistry.net. was kind enough to give us that information.
done TLD Parent Check Good. ns1.uniregistry.net., the parent server I interrogated, has information for your TLD.
done Your nameservers are listed Good. The parent server ns1.uniregistry.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.
add_alert DNS Parent sent Glue The parent nameserver ns1.uniregistry.net. is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
done Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS done NS records from your nameservers NS records got from your nameservers listed at the parent NS are:

noah.ns.cloudflare.com  ['108.162.193.133']   [TTL=1 days]
novalee.ns.cloudflare.com  ['108.162.194.182']   [TTL=1 days]

done Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
done 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!
warning Glue for NS records OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!
noah.ns.cloudflare.com[108.162.193.133]
novalee.ns.cloudflare.com[108.162.194.182]
done Mismatched NS records OK. The NS records at all your nameservers are identical.
done DNS servers responded Good. All nameservers listed at the parent server responded.
done Name of nameservers are valid OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!
done Multiple Nameservers Good. You have multiple nameserversAccording to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
done Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
done Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
done Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server ns1.uniregistry.net. are the same as the ones reported by your nameservers.
done 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.
done 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.
done Different subnets OK. Looks like you have nameservers on different subnets!
done 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
done 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.
done Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
done Stealth NS records sent Ok. No stealth ns records are sent
SOA add_alert SOA record The SOA record is:
Primary nameserver: noah.ns.cloudflare.com
Hostmaster E-mail address: [email protected]
Serial #: 2400788255
Refresh: 2 hours 46 minutes 40 seconds
Retry: 40 minutes
Expire: 7 days
Default TTL: 30 minutes
done NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2400788255.
done SOA MNAME entry OK. noah.ns.cloudflare.com That server is listed at the parent servers.
warning SOA Serial Your SOA serial number is: 2400788255 . This does not appears to be in the recommended format of YYYYMMDDnn.
done SOA REFRESH OK. Your SOA REFRESH interval is: 10000 . That is OK But recomended range is 1200-43200
done SOA RETRY Your SOA RETRY value is: 2400 . Looks ok But recomended range is 180-900
warning SOA EXPIRE Your SOA EXPIRE number is: 604800 seconds.Looks ok But recomended range is 1209600-2419200 seconds
done SOA MINIMUM TTL Your SOA MINIMUM TTL is: 1800 seconds. 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 1800 seconds is OK.
MX error MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
WWW add_alert WWW A Record Your www.datemij.link A record is:
datemij.link ->[104.21.20.61 172.67.191.211] [TTL:5 minutes 5 minutes]

done IPs are public OK. All of your WWW IPs appear to be public IPs.
done WWW CNAME OK. No CNAME
TXT done TXT Record
SRV done SRV Record Click To check SRV Record

Processed in (61.59 ms)