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



T

Timeout

Checked:
21.11.2020 21:33:15


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
misterikkese.duckdns.org
A
151.41.10.160
Florence/Tuscany/Italy (IT) - INFOSTRADA
No Hostname found
yes
1
0

AAAA

yes


www.misterikkese.duckdns.org
A
151.41.10.160
Florence/Tuscany/Italy (IT) - INFOSTRADA
No Hostname found
yes
1
0

AAAA

yes


*.misterikkese.duckdns.org
A
151.41.10.160
yes



AAAA

yes



CNAME

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 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2020, 00:00:00 +, Signature-Inception: 20.11.2020, 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: org
org
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2020, 17:00:00 +, Signature-Inception: 21.11.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 34266, Flags 256



Public Key with Algorithm 8, KeyTag 63858, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 08.12.2020, 15:32:12 +, Signature-Inception: 17.11.2020, 14:32:12 +, KeyTag 26974, Signer-Name: org



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest "T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: duckdns.org
duckdns.org
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 "oiil939ob7h9811kdjl2am675cpaul5h" between the hashed NSEC3-owner "oiikj44v7sdesa8n1e0rtujuk5sbqn7p" and the hashed NextOwner "oiinqimj9tcakvl98h1lc5726rq7vvie". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner oiikj44v7sdesa8n1e0rtujuk5sbqn7p.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.12.2020, 15:32:12 +, Signature-Inception: 17.11.2020, 14:32:12 +, KeyTag 63858, Signer-Name: org



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "d6n22mffurrkkhup4jscmntse266m0lq" as Owner. That's the Hash of "org" with the NextHashedOwnerName "d6n6gr81bv9d3ce1vsg6fn5bau7ub671". So that domain name is the Closest Encloser of "duckdns.org". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner d6n22mffurrkkhup4jscmntse266m0lq.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2020, 20:32:26 +, Signature-Inception: 21.11.2020, 19:32:26 +, KeyTag 63858, Signer-Name: org



0 DNSKEY RR found




Zone: misterikkese.duckdns.org
misterikkese.duckdns.org
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.misterikkese.duckdns.org
www.misterikkese.duckdns.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.misterikkese.duckdns.org
  ns1.duckdns.org


  ns2.duckdns.org


  ns3.duckdns.org

misterikkese.duckdns.org
  ns1.duckdns.org
54.187.92.222
Portland/Oregon/United States (US) - Amazon.com, Inc.


  ns2.duckdns.org
54.191.117.119
Portland/Oregon/United States (US) - Amazon.com, Inc.


  ns3.duckdns.org
52.26.169.94
Portland/Oregon/United States (US) - Amazon.com, Inc.

duckdns.org
T  ns1.duckdns.org
54.187.92.222
Portland/Oregon/United States (US) - Amazon.com, Inc.


  ns2.duckdns.org
54.191.117.119
Portland/Oregon/United States (US) - Amazon.com, Inc.


  ns3.duckdns.org
52.26.169.94
Portland/Oregon/United States (US) - Amazon.com, Inc.

org
  a0.org.afilias-nst.info / ns000b.app29.ams2.afilias-nst.info


  a2.org.afilias-nst.info / LHR8


  b0.org.afilias-nst.org / ns000b.app22.ams2.afilias-nst.info


  b2.org.afilias-nst.org / LHR7


  c0.org.afilias-nst.info / app1.iad1.hosts.meta.redstone.afilias-nst.info-2


  d0.org.afilias-nst.org / ns000b.app21.ams2.afilias-nst.info


4. SOA-Entries


Domain:org
Zone-Name:org
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2014153799
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:duckdns.org
Zone-Name:duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:3


Domain:misterikkese.duckdns.org
Zone-Name:duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:3


Domain:www.misterikkese.duckdns.org
Zone-Name:duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:3


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://misterikkese.duckdns.org/
151.41.10.160 GZip used - 476 / 1106 - 56.96 %
200

Html is minified: 136.54 %
1.906
H
small visible content (num chars: 20)
Temperatura: 20,3 °C
Date: Sat, 21 Nov 2020 20:45:05 GMT
Server: Apache/2.4.10 (Raspbian)
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 476
Connection: close
Content-Type: text/html; charset=UTF-8

• http://www.misterikkese.duckdns.org/
151.41.10.160 GZip used - 476 / 1106 - 56.96 %
200

Html is minified: 136.54 %
1.583
H
small visible content (num chars: 20)
Temperatura: 20,3 °C
Date: Sat, 21 Nov 2020 20:45:07 GMT
Server: Apache/2.4.10 (Raspbian)
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 476
Connection: close
Content-Type: text/html; charset=UTF-8

• https://misterikkese.duckdns.org/
151.41.10.160
-14

10.013
T
Timeout - The operation has timed out

• https://www.misterikkese.duckdns.org/
151.41.10.160
-14

10.030
T
Timeout - The operation has timed out

• http://misterikkese.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
151.41.10.160
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.097
A
Not Found
Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server. Apache/2.4.10 (Raspbian) Server at misterikkese.duckdns.org Port 80
Date: Sat, 21 Nov 2020 20:45:28 GMT
Server: Apache/2.4.10 (Raspbian)
Content-Length: 359
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.misterikkese.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
151.41.10.160
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.077
A
Not Found
Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server. Apache/2.4.10 (Raspbian) Server at www.misterikkese.duckdns.org Port 80
Date: Sat, 21 Nov 2020 20:45:28 GMT
Server: Apache/2.4.10 (Raspbian)
Content-Length: 363
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://151.41.10.160/
151.41.10.160
-14

10.030
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "misterikkese.duckdns.org" is domain, public suffix is ".duckdns.org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 4748 (complete: 131120)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: misterikkese.duckdns.org has only one ip address.
Warning: Only one ip address found: www.misterikkese.duckdns.org 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: misterikkese.duckdns.org has no ipv6 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: www.misterikkese.duckdns.org has no ipv6 address.
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 54.187.92.222: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org / 54.191.117.119: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 52.26.169.94: Timeout
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 misterikkese.duckdns.org, 1 ip addresses.
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 www.misterikkese.duckdns.org, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.duckdns.org (54.187.92.222), ns2.duckdns.org (54.191.117.119), ns3.duckdns.org (52.26.169.94)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, 3 Name Servers included in Delegation: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, 3 Name Servers included in 1 Zone definitions: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, 1 Name Servers listed in SOA.Primary: ns1.duckdns.org.
AGood: Only one SOA.Primary Name Server found.: ns1.duckdns.org.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.duckdns.org.
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: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org
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: 3 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 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.: 3 Name Servers, 1 Top Level Domain: duckdns.org
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:
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 52., 54., 3 different subnets (first two Bytes): 52.26., 54.187., 54.191., 3 different subnets (first three Bytes): 52.26.169., 54.187.92., 54.191.117.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
XNameserver Timeout checking Echo Capitalization: ns1.duckdns.org / 54.187.92.222
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 54.187.92.222: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 54.187.92.222: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 54.191.117.119: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 54.191.117.119: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 52.26.169.94: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 52.26.169.94: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
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.

3. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 765526 milliseconds, 765.526 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: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org

QNr.DomainTypeNS used
1
org
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
2
ns1.duckdns.org: 54.187.92.222
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns2.duckdns.org
54.191.117.119

Answer: ns3.duckdns.org
52.26.169.94


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.misterikkese.duckdns.org



1
0
misterikkese.duckdns.org



3
3
duckdns.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
misterikkese.duckdns.org

ok
1
0
www.misterikkese.duckdns.org

ok
1
0
_acme-challenge.misterikkese.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.www.misterikkese.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.misterikkese.duckdns.org.misterikkese.duckdns.org

perhaps wrong
1
0
_acme-challenge.www.misterikkese.duckdns.org.misterikkese.duckdns.org

perhaps wrong
1
0
_acme-challenge.www.misterikkese.duckdns.org.www.misterikkese.duckdns.org

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=57f7ea39-6992-4bfd-95f5-34b98ee5b9d5


Last Result: https://check-your-website.server-daten.de/?q=misterikkese.duckdns.org - 2020-11-21 21:33:15


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

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