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




T

Timeout

Checked:
14.06.2019 18:10:05


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
cloud2.hapsengewesen.net
A
185.162.229.124
Hvidovre/Hovedstaden/DK
Hostname: cloud2.hapsengewesen.net
yes
1
0

AAAA

yes


www.cloud2.hapsengewesen.net

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2019, 00:00:00, Signature-Inception: 10.06.2019, 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: net
net
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.06.2019, 05:00:00, Signature-Inception: 14.06.2019, 04:00:00, KeyTag 25266, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 2129, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.06.2019, 15:38:57, Signature-Inception: 09.06.2019, 15:33:57, KeyTag 35886, Signer-Name: net



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



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

Zone: hapsengewesen.net
hapsengewesen.net
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





Zone: cloud2.hapsengewesen.net
cloud2.hapsengewesen.net
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.cloud2.hapsengewesen.net
www.cloud2.hapsengewesen.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.cloud2.hapsengewesen.net
  ns11.domaincontrol.com

cloud2.hapsengewesen.net
  ns11.domaincontrol.com / p03
97.74.105.6
Scottsdale/Arizona/US


 
2603:5:2190::6
/US

hapsengewesen.net
  ns11.domaincontrol.com / p01


  ns12.domaincontrol.com / p22

net
  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


4. SOA-Entries


Domain:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1560528584
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:9


Domain:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1560528599
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:hapsengewesen.net
Primary:ns11.domaincontrol.com
Mail:dns.jomax.net
Serial:2019041303
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:2


Domain:cloud2.hapsengewesen.net
Primary:ns11.domaincontrol.com
Mail:dns.jomax.net
Serial:2019041303
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:2


5. Url-Checks

Domainname Http-StatusredirectSec.G
• http://cloud2.hapsengewesen.net/
185.162.229.124
-14

10.013
T
Timeout - The operation has timed out

• https://cloud2.hapsengewesen.net/
185.162.229.124
-14

10.017
T
Timeout - The operation has timed out

• http://cloud2.hapsengewesen.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.162.229.124
-14

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

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "cloud2.hapsengewesen.net" is subdomain, public suffix is "net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
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: ns11.domaincontrol.com: 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.
http://cloud2.hapsengewesen.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.162.229.124
-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.
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: 57890 milliseconds, 57.890 seconds


7. Connections (http/2- and additional Tls.1.0/1.1/1.2 checks are BETA)

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
823925530
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-22 06:15:26
2019-06-20 06:15:26
cloud2.hapsengewesen.net, www2.hapsengewesen.net - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow (currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1331230942
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-22 05:15:26
2019-06-20 04:15:26
cloud2.hapsengewesen.net, www2.hapsengewesen.net
2 entries


1127917377
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-01-20 11:57:47
2019-04-20 10:57:47
cloud2.hapsengewesen.net, www2.hapsengewesen.net
2 entries


426605909
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-04-26 13:40:59
2018-07-25 13:40:59
cloud2.hapsengewesen.net, www2.hapsengewesen.net
2 entries



10. Html-Content - Entries

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cloud2.hapsengewesen.net
0

no CAA entry found
1
0
hapsengewesen.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
hapsengewesen.net

ok
1
0
cloud2.hapsengewesen.net

ok
1
0
_acme-challenge.cloud2.hapsengewesen.net

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud2.hapsengewesen.net.hapsengewesen.net

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud2.hapsengewesen.net.cloud2.hapsengewesen.net

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=0d839263-088e-4f26-a0e3-e0738fb2fcb2


Last Result: https://check-your-website.server-daten.de/?q=cloud2.hapsengewesen.net - 2019-06-14 18:10:05


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

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