Check DNS, Urls + Redirects, Certificates and Content of your Website




1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
synology.me
A

yes
1
0

AAAA

yes


www.synology.me

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 14748, Flags 256



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2021, 00:00:00 +, Signature-Inception: 20.11.2021, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: me
me
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 45352, DigestType 2 and Digest dwjIptXXK2MhS7/1DLVFU/fgeh+l6QdL2NY8QxAthVk=



1 RRSIG RR to validate DS RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.12.2021, 05:00:00 +, Signature-Inception: 27.11.2021, 04:00:00 +, KeyTag 14748, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 14748 used to validate the DS RRSet in the parent zone



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 27963, Flags 256



Public Key with Algorithm 8, KeyTag 45352, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 49263, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 16.12.2021, 15:34:38 +, Signature-Inception: 25.11.2021, 14:34:38 +, KeyTag 45352, Signer-Name: me



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 45352 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 45352, DigestType 2 and Digest "dwjIptXXK2MhS7/1DLVFU/fgeh+l6QdL2NY8QxAthVk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: synology.me
synology.me
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "fiqbh6d8u76bm19kibqnqe3a17pr81vi" between the hashed NSEC3-owner "fip56gou1q5jedefbo4fd7d3831ig0ov" and the hashed NextOwner "fiqnlkrcaq5jtss06icmpqg41v2r9hdi". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fip56gou1q5jedefbo4fd7d3831ig0ov.me., Algorithm: 8, 2 Labels, original TTL: 8400 sec, Signature-expiration: 16.12.2021, 15:34:38 +, Signature-Inception: 25.11.2021, 14:34:38 +, KeyTag 27963, Signer-Name: me



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "vglcc2i8cv74h28k6oahf7ooleaffnq4" as Owner. That's the Hash of "me" with the NextHashedOwnerName "vgle74ah38rvq5cugt3bjuth2nlrovq6". So that domain name is the Closest Encloser of "synology.me". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner vglcc2i8cv74h28k6oahf7ooleaffnq4.me., Algorithm: 8, 2 Labels, original TTL: 8400 sec, Signature-expiration: 18.12.2021, 21:41:52 +, Signature-Inception: 27.11.2021, 20:41:52 +, KeyTag 27963, Signer-Name: me



0 DNSKEY RR found




Zone: www.synology.me
www.synology.me
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.synology.me
  ddns-ns1.quickconnect.to

synology.me
  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC


  ddns-ns2.quickconnect.to
68.183.254.129
London/England/United Kingdom (GB) - DigitalOcean, LLC

me
  a0.nic.me


  a2.nic.me


  b0.nic.me


  b2.nic.me


  c0.nic.me


4. SOA-Entries


Domain:me
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:5


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:1155183282
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:1155183283
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:www.synology.me
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "synology.me" is public suffix, public suffix is ".synology.me", top-level-domain is ".me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro", num .me-domains preloaded: 1691 (complete: 168171)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem

2. DNS- and NameServer - Checks

AGood: Only one SOA.Primary Name Server found.: ddns-ns1.quickconnect.to.
AGood: SOA.Primary Name Server included in the delegation set.: ddns-ns1.quickconnect.to.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: to
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: quickconnect.to
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, GB
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a0.nic.me: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: a2.nic.me: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: b0.nic.me: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: b2.nic.me: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: c0.nic.me: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
XFatal error: Nameservers with different SOA Serial Numbers
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

ADuration: 15994 milliseconds, 15.994 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
synology.me
0

no CAA entry found
1
0
me
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
_acme-challenge.synology.me

Name Error - The domain name does not exist
1
0
_acme-challenge.synology.me.synology.me

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=a77093eb-c742-46f2-a510-909cbf83fd1e


Last Result: https://check-your-website.server-daten.de/?q=synology.me - 2021-11-27 22:45:01


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=synology.me" target="_blank">Check this Site: synology.me</a>