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




T

Timeout

Checked:
25.01.2023 05:18:57


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
sethkj.synology.me
A
67.180.60.169
San Francisco/California/United States (US) - Comcast Cable Communications, LLC
Hostname: c-67-180-60-169.hsd1.ca.comcast.net
yes
1
0

AAAA

yes


www.sethkj.synology.me

Name Error
yes
1
0
www.sethkj.synology.me
A
67.180.60.169
San Francisco/California/United States (US) - Comcast Cable Communications, LLC
No Hostname found
no


*.sethkj.synology.me
A
67.180.60.169
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 951, 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.02.2023, 00:00:00 +, Signature-Inception: 21.01.2023, 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: 06.02.2023, 22:00:00 +, Signature-Inception: 24.01.2023, 21:00:00 +, KeyTag 951, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 11895, Flags 256



Public Key with Algorithm 8, KeyTag 18651, 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: 900 sec, Signature-expiration: 07.02.2023, 15:31:23 +, Signature-Inception: 17.01.2023, 14:31:23 +, 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 "fiq4sfd45ua9282rsvkgpo0430dfi4ov" and the hashed NextOwner "fiqnlkrcaq5jtss06icmpqg41v2r9hdi". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fiq4sfd45ua9282rsvkgpo0430dfi4ov.me., Algorithm: 8, 2 Labels, original TTL: 8400 sec, Signature-expiration: 07.02.2023, 15:31:23 +, Signature-Inception: 17.01.2023, 14:31:23 +, KeyTag 11895, 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: 15.02.2023, 04:17:21 +, Signature-Inception: 25.01.2023, 03:17:21 +, KeyTag 11895, Signer-Name: me



0 DNSKEY RR found




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



0 DNSKEY RR found




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


3. Name Servers

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

sethkj.synology.me
  ddns-ns1.quickconnect.to
161.35.216.33
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


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


  ddns-ns3.quickconnect.to
139.59.136.221
Frankfurt am Main/Hesse/Germany (DE) - DIGITALOCEAN


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

me
  a0.nic.me / app15.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  a2.nic.me / FRA3


  b0.nic.me / app22.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  b2.nic.me / FRA3


  c0.nic.me / app31.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  ns.nic.me


4. SOA-Entries


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


Domain:me
Zone-Name:me
Primary:ns.nic.me
Mail:noc.afilias-nst.info
Serial:2011366003
Refresh:3600
Retry:3600
Expire:3600000
TTL:8400
num Entries:5


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:1753217536
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:1753217536
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:1753217633
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:2


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


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:1753217634
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:1753217634
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


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


Domain:www.sethkj.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
• http://sethkj.synology.me/
67.180.60.169
-14

10.064
T
Timeout - The operation has timed out

• http://www.sethkj.synology.me/
67.180.60.169
-14

10.034
T
Timeout - The operation has timed out

• https://sethkj.synology.me/
67.180.60.169
-14

10.044
T
Timeout - The operation has timed out

• https://www.sethkj.synology.me/
67.180.60.169
-14

10.037
T
Timeout - The operation has timed out

• http://sethkj.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
67.180.60.169
-14

10.050
T
Timeout - The operation has timed out
Visible Content:

• http://www.sethkj.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
67.180.60.169
-14

10.037
T
Timeout - The operation has timed out
Visible Content:

• https://67.180.60.169/
67.180.60.169
-14

10.043
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "sethkj.synology.me" is domain, 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: 1927 (complete: 216710)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: sethkj.synology.me has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: sethkj.synology.me has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "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.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain sethkj.synology.me, 1 ip addresses.
BNo _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.sethkj.synology.me

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 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.
AInfo:: 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.
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, ddns-ns3.quickconnect.to, ddns-ns4.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: 4 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 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.: 4 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: 4 Name Servers, 2 Countries: DE, GB
AInfo: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 138., 139., 161., 3 different subnets (first two Bytes): 138.68., 139.59., 161.35., 4 different subnets (first three Bytes): 138.68.128., 138.68.173., 139.59.136., 161.35.216.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
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: ns.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.
AGood: 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://sethkj.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 67.180.60.169
-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.sethkj.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 67.180.60.169
-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.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 144010 milliseconds, 144.010 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)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
1
13
13

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4728789642
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-25 03:13:32
2023-04-25 03:13:31
sethkj.synology.me - 1 entries
duplicate nr. 1

4722847363
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 22:16:46
2023-04-23 22:16:45
*.sethkj.synology.me, sethkj.synology.me - 2 entries


4722847898
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 22:16:44
2023-04-23 22:16:43
*.sethkj.synology.me, sethkj.synology.me - 2 entries


4722528168
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 21:08:02
2023-04-23 21:08:01
sethkj.synology.me - 1 entries


4722528109
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 21:08:00
2023-04-23 21:07:59
sethkj.synology.me - 1 entries


4722527756
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 21:07:48
2023-04-23 21:07:47
sethkj.synology.me - 1 entries


4722527696
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 21:07:46
2023-04-23 21:07:45
sethkj.synology.me - 1 entries


4692921904
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-17 06:09:01
2023-04-17 06:09:00
sethkj.synology.me - 1 entries


4692918947
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-01-17 06:08:59
2023-04-17 06:08:58
sethkj.synology.me - 1 entries


4450109140
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-21 11:31:15
2023-02-19 11:31:14
sethkj.synology.me - 1 entries


4450104779
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-21 11:31:14
2023-02-19 11:31:13
sethkj.synology.me - 1 entries


4413202607
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-12 20:51:22
2023-02-10 20:51:21
sethkj.synology.me - 1 entries


4413205681
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-12 20:51:21
2023-02-10 20:51:20
sethkj.synology.me - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
10
34

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
8481104915
precert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 20:08:02
2023-04-23 19:08:01
sethkj.synology.me
1 entries


8481104972
precert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 20:08:00
2023-04-23 19:07:59
sethkj.synology.me
1 entries


8481102528
precert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 20:07:48
2023-04-23 19:07:47
sethkj.synology.me
1 entries


8481102386
precert
CN=R3, O=Let's Encrypt, C=US
2023-01-23 20:07:46
2023-04-23 19:07:45
sethkj.synology.me
1 entries


8451750874
precert
CN=R3, O=Let's Encrypt, C=US
2023-01-17 05:09:01
2023-04-17 04:09:00
sethkj.synology.me
1 entries


8427847855
precert
CN=R3, O=Let's Encrypt, C=US
2023-01-17 05:08:59
2023-04-17 04:08:58
sethkj.synology.me
1 entries


8029025866
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-21 10:31:15
2023-02-19 10:31:14
sethkj.synology.me
1 entries


8029025991
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-21 10:31:14
2023-02-19 10:31:13
sethkj.synology.me
1 entries


7962106156
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-12 19:51:22
2023-02-10 19:51:21
sethkj.synology.me
1 entries


7962167150
precert
CN=R3, O=Let's Encrypt, C=US
2022-11-12 19:51:21
2023-02-10 19:51:20
sethkj.synology.me
1 entries


7553913820
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-09-16 08:06:49
2022-12-15 09:06:48
sethkj.synology.me
1 entries


7553917736
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-09-16 08:06:47
2022-12-15 09:06:46
sethkj.synology.me
1 entries


7506020055
precert
CN=R3, O=Let's Encrypt, C=US
2022-09-09 10:06:30
2022-12-08 11:06:29
sethkj.synology.me
1 entries


7506020274
precert
CN=R3, O=Let's Encrypt, C=US
2022-09-09 10:06:28
2022-12-08 11:06:27
sethkj.synology.me
1 entries


7149767850
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-18 07:53:29
2022-10-16 07:53:28
sethkj.synology.me
1 entries


7149767941
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-18 07:53:28
2022-10-16 07:53:27
sethkj.synology.me
1 entries


7096053082
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-09 16:33:50
2022-10-07 16:33:49
sethkj.synology.me
1 entries


7096053113
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-09 16:33:48
2022-10-07 16:33:47
sethkj.synology.me
1 entries


6759519692
precert
CN=R3, O=Let's Encrypt, C=US
2022-05-19 03:29:51
2022-08-17 03:29:50
sethkj.synology.me
1 entries


6759521579
precert
CN=R3, O=Let's Encrypt, C=US
2022-05-19 03:29:49
2022-08-17 03:29:48
sethkj.synology.me
1 entries


6759519377
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-05-19 03:29:45
2022-08-17 03:29:44
sethkj.synology.me
1 entries


6759521563
precert
CN=R3, O=Let's Encrypt, C=US
2022-05-19 03:29:43
2022-08-17 03:29:42
sethkj.synology.me
1 entries


6369443357
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-03-18 14:40:42
2022-06-16 13:40:41
sethkj.synology.me
1 entries


6369442543
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-03-18 14:40:41
2022-06-16 13:40:40
sethkj.synology.me
1 entries


6369445806
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-03-18 14:40:38
2022-06-16 13:40:37
sethkj.synology.me
1 entries


6369445832
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-03-18 14:40:37
2022-06-16 13:40:36
sethkj.synology.me
1 entries


5990789104
precert
CN=R3, O=Let's Encrypt, C=US
2022-01-16 12:48:28
2022-04-16 11:48:27
sethkj.synology.me
1 entries


5990785610
precert
CN=R3, O=Let's Encrypt, C=US
2022-01-16 12:48:26
2022-04-16 11:48:25
sethkj.synology.me
1 entries


5990785673
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-01-16 12:48:24
2022-04-16 11:48:23
sethkj.synology.me
1 entries


5990785073
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-01-16 12:48:23
2022-04-16 11:48:22
sethkj.synology.me
1 entries


5621516219
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-11-16 19:00:28
2022-02-14 19:00:27
sethkj.synology.me
1 entries


5621517243
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-11-16 19:00:26
2022-02-14 19:00:25
sethkj.synology.me
1 entries


5621516585
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-11-16 19:00:23
2022-02-14 19:00:22
sethkj.synology.me
1 entries


5621516156
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-11-16 19:00:22
2022-02-14 19:00:21
sethkj.synology.me
1 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.DomainTypeNS used
1
to
NS
f.root-servers.net (2001:500:2f::f)

Answer: colo.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
colo.tonic.to (216.74.32.101)

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
colo.tonic.to (216.74.32.101)

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
colo.tonic.to (216.74.32.101)

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
colo.tonic.to (216.74.32.101)

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
b.root-servers.net (2001:500:200::b)

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
k.root-servers.net (2001:7fd::1)

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
j.root-servers.net (2001:503:c27::2:30)

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
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: 138.68.173.245
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
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: 138.68.128.239
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

DomainnameflagNameValue∑ Queries∑ Timeout
sethkj.synology.me
0

no CAA entry found
1
0
synology.me
0

no CAA entry found
1
0
me
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
sethkj.synology.me

ok
1
0
_acme-challenge.sethkj.synology.me

missing entry or wrong length
1
0
_acme-challenge.sethkj.synology.me.sethkj.synology.me

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
_dmarc
TXT
_dmarc.sethkj.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=4a54e12b-47c4-40c2-bb6b-a7a48d02aa42


Last Result: https://check-your-website.server-daten.de/?q=sethkj.synology.me - 2023-01-25 05:18:57


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

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