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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
12.02.2024 11:33:04

Older results

V - 12.02.2024 10:59:42

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
ha.hellie4u.synology.me		Name Error	yes	1	0
www.ha.hellie4u.synology.me		Name Error	yes	1	0
ha.hellie4u.synology.me	A	31.21.236.102 The Hague/South Holland/The Netherlands (NL) - TMONL No Hostname found	no
www.ha.hellie4u.synology.me	A	31.21.236.102 The Hague/South Holland/The Netherlands (NL) - TMONL No Hostname found	no
*.hellie4u.synology.me	A	31.21.236.102	yes
	AAAA		yes
	CNAME	Name Error	yes
*.ha.hellie4u.synology.me	A	31.21.236.102	yes
	AAAA		yes
	CNAME	Name Error	yes

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 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 30903, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.03.2024, 00:00:00 +, Signature-Inception: 10.02.2024, 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: 25.02.2024, 05:00:00 +, Signature-Inception: 12.02.2024, 04:00:00 +, KeyTag 30903, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 12693, Flags 256


	Public Key with Algorithm 8, KeyTag 12819, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 01.03.2024, 15:43:40 +, Signature-Inception: 09.02.2024, 14:43:40 +, 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 "483mluc2de6mvkn4q8bgsfp856adurvb" between the hashed NSEC3-owner "483m5k303iaocn2ep5s47agdj8982c9d" and the hashed NextOwner "4848siul4sp22qb7n2cvah2i7d9013e7". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 483m5k303iaocn2ep5s47agdj8982c9d.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 01.03.2024, 15:43:40 +, Signature-Inception: 09.02.2024, 14:43:40 +, KeyTag 12693, Signer-Name: me


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "c0aa63slu8ucpmm55hrueae8tj5iopm2" as Owner. That's the Hash of "me" with the NextHashedOwnerName "c0ajt0t91msh2hqlhlmc6k9ht14h00t4". So that domain name is the Closest Encloser of "synology.me". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner c0aa63slu8ucpmm55hrueae8tj5iopm2.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 04.03.2024, 10:25:10 +, Signature-Inception: 12.02.2024, 09:25:10 +, KeyTag 12693, Signer-Name: me


	0 DNSKEY RR found




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


	0 DNSKEY RR found




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

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

3. Name Servers

Domain	Nameserver	NS-IP
www.ha.hellie4u.synology.me	• ddns-ns1.quickconnect.to
ha.hellie4u.synology.me	• ddns-ns1.quickconnect.to
hellie4u.synology.me	T ddns-ns1.quickconnect.to	161.35.216.33 Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC	•
	•	164.92.178.233 Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC	•
synology.me	• ddns-ns1.quickconnect.to	161.35.216.33 Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC	•
	•	164.92.178.233 Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC	•
	• ddns-ns2.quickconnect.to	165.232.102.219 Slough/England/United Kingdom (GB) - DigitalOcean, LLC	•
	•	167.99.90.184 Slough/England/United Kingdom (GB) - DigitalOcean, LLC	•
	• ddns-ns3.quickconnect.to	139.59.136.221 Frankfurt am Main/Hesse/Germany (DE) - DIGITALOCEAN	•
	•	164.92.130.229 Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC	•
	• ddns-ns4.quickconnect.to	167.99.201.119 Slough/England/United Kingdom (GB) - DigitalOcean, LLC	•
	•	167.99.85.248 Slough/England/United Kingdom (GB) - DigitalOcean, LLC	•
me	• a0.nic.me / app23.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• a2.nic.me / FRA6		•
	• b0.nic.me / app31.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• b2.nic.me / FRA3		•
	• c0.nic.me / app6.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•

4. SOA-Entries

Domain:	me
Zone-Name:	me
Primary:	a0.nic.me
Mail:	hostmaster.donuts.email
Serial:	1707733290
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	5

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

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

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

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

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

Domain:	www.ha.hellie4u.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

Domainname	Http-Status	Sec.	G
• http://ha.hellie4u.synology.me/ 31.21.236.102	-14	10.013	T
Timeout - The operation has timed out.

• http://www.ha.hellie4u.synology.me/ 31.21.236.102	-14	10.004	T
Timeout - The operation has timed out.

• https://ha.hellie4u.synology.me/ 31.21.236.102	-16	1.233	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:31.21.236.102]:443 (31.21.236.102:443)

• https://www.ha.hellie4u.synology.me/ 31.21.236.102	-16	1.326	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:31.21.236.102]:443 (31.21.236.102:443)

• http://ha.hellie4u.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 31.21.236.102	-14	10.017	T
Timeout - The operation has timed out.
Visible Content:

• http://www.ha.hellie4u.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 31.21.236.102	-14	10.013	T
Timeout - The operation has timed out.
Visible Content:

• https://31.21.236.102/ 31.21.236.102	-16	1.390	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:31.21.236.102]:443 (31.21.236.102:443)

7. Comments

	1. General Results, most used to calculate the result
A	name "ha.hellie4u.synology.me" is subdomain, 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: 2062 (complete: 239099)
A	Good: All ip addresses are public addresses
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.ha.hellie4u.synology.me
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 29 Queries complete, 25 with IPv6, 4 with IPv4.
	Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
	Ok (4 - 8):: An average of 7.3 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, ddns-ns3.quickconnect.to, ddns-ns4.quickconnect.to, 4 Name Servers included in Delegation: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, ddns-ns3.quickconnect.to, ddns-ns4.quickconnect.to, 4 Name Servers included in 1 Zone definitions: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, ddns-ns3.quickconnect.to, ddns-ns4.quickconnect.to, 1 Name Servers listed in SOA.Primary: ddns-ns1.quickconnect.to.
A	Good: Only one SOA.Primary Name Server found.: ddns-ns1.quickconnect.to.
A	Good: SOA.Primary Name Server included in the delegation set.: ddns-ns1.quickconnect.to.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Info: Ipv4-Subnet-list: 8 Name Servers, 5 different subnets (first Byte): 139., 161., 164., 165., 167., 5 different subnets (first two Bytes): 139.59., 161.35., 164.92., 165.232., 167.99., 8 different subnets (first three Bytes): 139.59.136., 161.35.216., 164.92.130., 164.92.178., 165.232.102., 167.99.201., 167.99.85., 167.99.90.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Good: Nameserver supports TCP connections: 2 good Nameserver
X	Nameserver Timeout checking Echo Capitalization: ddns-ns1.quickconnect.to / 161.35.216.33
X	Nameserver Timeout checking EDNS512: ddns-ns1.quickconnect.to / 161.35.216.33
	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.
	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.
	Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to / 161.35.216.33: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
A	Good: All SOA have the same Serial Number
	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.
	4. Content- and Performance-critical Checks
	http://ha.hellie4u.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 31.21.236.102	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.ha.hellie4u.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 31.21.236.102	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 265687 milliseconds, 265.687 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)

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0	0	15

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
6739757998 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 07:31:57	2024-05-12 07:31:56	*.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6739764009 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 07:31:52	2024-05-12 07:31:51	*.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6739679133 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 07:13:28	2024-05-12 07:13:27	ha.hellie4u.synology.me - 1 entries
6739674512 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 07:13:25	2024-05-12 07:13:24	ha.hellie4u.synology.me - 1 entries
6737371654 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 20:54:04	2024-05-11 20:54:03	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6737370322 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 20:54:00	2024-05-11 20:53:59	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6737185262 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 19:55:35	2024-05-11 19:55:34	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6737185046 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 19:55:31	2024-05-11 19:55:30	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6632082620 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 22:41:01	2024-04-24 22:41:00	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6632072776 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 22:39:26	2024-04-24 22:39:25	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6632072691 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 22:39:23	2024-04-24 22:39:22	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6631454891 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 20:12:08	2024-04-24 20:12:07	*.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6631452385 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 20:12:04	2024-04-24 20:12:03	*.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6629342529 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 12:26:57	2024-04-24 12:26:56	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries
6629339623 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 12:26:54	2024-04-24 12:26:53	ha.hellie4u.synology.me, hellie4u.synology.me - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	17

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12053666256 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 08:05:01	2024-05-12 07:05:00	*.hellie4u.synology.me, hellie4u.synology.me 2 entries
12053664650 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 08:04:57	2024-05-12 07:04:56	*.hellie4u.synology.me, hellie4u.synology.me 2 entries
12052995521 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 06:31:57	2024-05-12 05:31:56	*.hellie4u.synology.me, hellie4u.synology.me 2 entries
12052998360 precert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 06:31:52	2024-05-12 05:31:51	*.hellie4u.synology.me, hellie4u.synology.me 2 entries
12052859726 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 06:13:28	2024-05-12 05:13:27	ha.hellie4u.synology.me 1 entries
12052859785 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-12 06:13:25	2024-05-12 05:13:24	ha.hellie4u.synology.me 1 entries
12048866932 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 19:54:04	2024-05-11 18:54:03	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
12048870713 precert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 19:54:00	2024-05-11 18:53:59	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
12048549242 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 18:55:35	2024-05-11 17:55:34	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
12048553111 precert	CN=R3, O=Let's Encrypt, C=US	2024-02-11 18:55:31	2024-05-11 17:55:30	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
11868448749 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 21:41:01	2024-04-24 20:41:00	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
11868439907 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 21:39:26	2024-04-24 20:39:25	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
11868441084 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 21:39:23	2024-04-24 20:39:22	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
11867359525 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 19:12:08	2024-04-24 18:12:07	*.hellie4u.synology.me, hellie4u.synology.me 2 entries
11867361963 precert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 19:12:04	2024-04-24 18:12:03	*.hellie4u.synology.me, hellie4u.synology.me 2 entries
11863679976 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 11:26:57	2024-04-24 10:26:56	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries
11863679531 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-25 11:26:54	2024-04-24 10:26:53	ha.hellie4u.synology.me, hellie4u.synology.me 2 entries

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: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, ddns-ns3.quickconnect.to, ddns-ns4.quickconnect.to

QNr.	Domain	Type	NS used
1	to	NS	k.root-servers.net (2001:7fd::1)
	Answer: cd5.tonic.to, cd6.tonic.to, cd7.tonic.to, cd8.tonic.to, frankfurt.tonic.to, helsinki.tonic.to, newyork.tonic.to, singapore.tonic.to, sydney.tonic.to, tonic.to
2	ddns-ns1.quickconnect.to	NS	cd5.tonic.to (185.136.96.197)
	Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
3	ddns-ns2.quickconnect.to	NS	cd5.tonic.to (185.136.96.197)
	Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
4	ddns-ns3.quickconnect.to	NS	cd5.tonic.to (185.136.96.197)
	Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
5	ddns-ns4.quickconnect.to	NS	cd5.tonic.to (185.136.96.197)
	Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
6	org	NS	c.root-servers.net (2001:500:2::c)
	Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
7	ns-1412.awsdns-48.org	NS	a0.org.afilias-nst.info (2001:500:e::1)
	Answer: g-ns-1075.awsdns-48.org, g-ns-1648.awsdns-48.org, g-ns-176.awsdns-48.org, g-ns-754.awsdns-48.org
	Answer: g-ns-1075.awsdns-48.org 205.251.196.51, 2600:9000:5304:3300::1
	Answer: g-ns-1648.awsdns-48.org 205.251.198.112, 2600:9000:5306:7000::1
	Answer: g-ns-176.awsdns-48.org 205.251.192.176, 2600:9000:5300:b000::1
	Answer: g-ns-754.awsdns-48.org 205.251.194.242, 2600:9000:5302:f200::1
8	uk	NS	b.root-servers.net (2001:500:200::b)
	Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
9	ns-1987.awsdns-56.co.uk	NS	dns1.nic.uk (2a01:618:400::1)
	Answer: g-ns-1531.awsdns-56.co.uk, g-ns-1852.awsdns-56.co.uk, g-ns-376.awsdns-56.co.uk, g-ns-952.awsdns-56.co.uk
	Answer: g-ns-1531.awsdns-56.co.uk 205.251.197.251, 2600:9000:5305:fb00::1
	Answer: g-ns-1852.awsdns-56.co.uk 205.251.199.60, 2600:9000:5307:3c00::1
	Answer: g-ns-376.awsdns-56.co.uk 205.251.193.120, 2600:9000:5301:7800::1
	Answer: g-ns-952.awsdns-56.co.uk 205.251.195.184, 2600:9000:5303:b800::1
10	com	NS	d.root-servers.net (2001:500:2d::d)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
11	ns-55.awsdns-06.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: g-ns-1158.awsdns-06.com, g-ns-1734.awsdns-06.com, g-ns-582.awsdns-06.com, g-ns-7.awsdns-06.com
	Answer: g-ns-1158.awsdns-06.com 205.251.196.134, 2600:9000:5304:8600::1
	Answer: g-ns-1734.awsdns-06.com 205.251.198.198, 2600:9000:5306:c600::1
	Answer: g-ns-582.awsdns-06.com 205.251.194.70, 2600:9000:5302:4600::1
	Answer: g-ns-7.awsdns-06.com 205.251.192.7, 2600:9000:5300:700::1
12	net	NS	l.root-servers.net (2001:500:9f::42)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
13	ns-597.awsdns-10.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: g-ns-1354.awsdns-10.net, g-ns-1930.awsdns-10.net, g-ns-459.awsdns-10.net, g-ns-780.awsdns-10.net
	Answer: g-ns-1354.awsdns-10.net 205.251.197.74, 2600:9000:5305:4a00::1
	Answer: g-ns-1930.awsdns-10.net 205.251.199.138, 2600:9000:5307:8a00::1
	Answer: g-ns-459.awsdns-10.net 205.251.193.203, 2600:9000:5301:cb00::1
	Answer: g-ns-780.awsdns-10.net 205.251.195.12, 2600:9000:5303:c00::1
14	ns-1412.awsdns-48.org: 205.251.197.132	A	g-ns-1075.awsdns-48.org (2600:9000:5304:3300::1)
15	ns-1412.awsdns-48.org: 2600:9000:5305:8400::1	AAAA	g-ns-1075.awsdns-48.org (2600:9000:5304:3300::1)
16	ns-1987.awsdns-56.co.uk: 205.251.199.195	A	g-ns-1531.awsdns-56.co.uk (2600:9000:5305:fb00::1)
17	ns-1987.awsdns-56.co.uk: 2600:9000:5307:c300::1	AAAA	g-ns-1531.awsdns-56.co.uk (2600:9000:5305:fb00::1)
18	ns-55.awsdns-06.com: 205.251.192.55	A	g-ns-1158.awsdns-06.com (2600:9000:5304:8600::1)
19	ns-55.awsdns-06.com: 2600:9000:5300:3700::1	AAAA	g-ns-1158.awsdns-06.com (2600:9000:5304:8600::1)
20	ns-597.awsdns-10.net: 205.251.194.85	A	g-ns-1354.awsdns-10.net (2600:9000:5305:4a00::1)
21	ns-597.awsdns-10.net: 2600:9000:5302:5500::1	AAAA	g-ns-1354.awsdns-10.net (2600:9000:5305:4a00::1)
22	ddns-ns1.quickconnect.to: 161.35.216.33, 164.92.178.233	A	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
23	ddns-ns1.quickconnect.to: No AAAA record found	AAAA	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
24	ddns-ns2.quickconnect.to: 165.232.102.219, 167.99.90.184	A	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
25	ddns-ns2.quickconnect.to: No AAAA record found	AAAA	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
26	ddns-ns3.quickconnect.to: 139.59.136.221, 164.92.130.229	A	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
27	ddns-ns3.quickconnect.to: No AAAA record found	AAAA	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
28	ddns-ns4.quickconnect.to: 167.99.201.119, 167.99.85.248	A	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
29	ddns-ns4.quickconnect.to: No AAAA record found	AAAA	ns-1412.awsdns-48.org (2600:9000:5305:8400::1)

13. CAA - Entries

Domainname	Value	∑ Queries
hellie4u.synology.me	no CAA entry found	1
synology.me	no CAA entry found	1
me	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
hellie4u.synology.me		ok	1	0
_acme-challenge.ha.hellie4u.synology.me.hellie4u.synology.me		Name Error - The domain name does not exist	1	0

15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06, SMTP-TLS-Reporting is alpa - 2024-07-13)

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
_dmarc	TXT	_dmarc.ha.hellie4u.synology.me			0	0	ok

16. Cipher Suites

No results

17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=13ebaeb3-484a-46f5-9e5a-8aa01d7ea7dc

Last Result: https://check-your-website.server-daten.de/?q=ha.hellie4u.synology.me - 2024-02-12 11:33:04

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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=ha.hellie4u.synology.me