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




T

Timeout

Checked:
12.02.2019 02:54:28


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
um.myfirewall.org
A
93.216.142.45
Hostname: p5dd88e2d.dip0.t-ipconnect.de
yes
1
0

AAAA
2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69

yes


www.um.myfirewall.org

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(root)
1 DS RR published

Status: Valid because published

3 DNSKEY RR found

Public Key with Algorithm 8, KeyTag 16749, Flags 256

Public Key with Algorithm 8, KeyTag 19164, Flags 385

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

2 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 03.03.2019, 00:00:00, Signature-Inception: 10.02.2019, 00:00:00, KeyTag 19164, Signer-Name: (root)

Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 03.03.2019, 00:00:00, Signature-Inception: 10.02.2019, 00:00:00, KeyTag 20326, Signer-Name: (root)

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

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
org
2 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: 24.02.2019, 21:00:00, Signature-Inception: 11.02.2019, 20:00:00, KeyTag 16749, Signer-Name: (root)

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

4 DNSKEY RR found

Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)

Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)

Public Key with Algorithm 7, KeyTag 27764, Flags 256

Public Key with Algorithm 7, KeyTag 44603, Flags 256

3 RRSIG RR to validate DNSKEY RR found

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 02.03.2019, 15:22:07, Signature-Inception: 09.02.2019, 14:22:07, KeyTag 9795, Signer-Name: org

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 02.03.2019, 15:22:07, Signature-Inception: 09.02.2019, 14:22:07, KeyTag 17883, Signer-Name: org

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 02.03.2019, 15:22:07, Signature-Inception: 09.02.2019, 14:22:07, KeyTag 44603, Signer-Name: org

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 44603 used to validate the DNSKEY RRSet

Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
myfirewall.org
0 DS RR in the parent zone found

0 DNSKEY RR found


um.myfirewall.org
0 DS RR in the parent zone found

0 DNSKEY RR found


www.um.myfirewall.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.um.myfirewall.org
  dyndns.securepoint.de

um.myfirewall.org
  dyndns.securepoint.de
213.128.147.60

 
2001:868:100:901:53::1
myfirewall.org
  dns-001.securepoint.de / mhwserv01.mhw.de


  dyndns.securepoint.de


  ns1.m-online.net / ns1.m-online.net


  ns2.m-online.net / ns2.m-online.net


  ns3.m-online.net


  ns4.m-online.net / ns4.m-online.net

org
  a0.org.afilias-nst.info / ns000b.app21.mia2.afilias-nst.info


  a2.org.afilias-nst.info / 2.ber.pch


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


  b2.org.afilias-nst.org / 4.fra.pch


  c0.org.afilias-nst.info / ns000b.app3.ams2.afilias-nst.info


  d0.org.afilias-nst.org / ns000b.app6.iad1.afilias-nst.info


4. SOA-Entries


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


Domain:myfirewall.org
Primary:dyndns.securepoint.de
Mail:hostmaster.securepoint.de
Serial:1435038679
Refresh:180
Retry:180
Expire:604800
TTL:180
num Entries:1


Domain:myfirewall.org
Primary:dyndns.securepoint.de
Mail:hostmaster.securepoint.de
Serial:1435038684
Refresh:180
Retry:180
Expire:604800
TTL:180
num Entries:5


Domain:um.myfirewall.org
Primary:dyndns.securepoint.de
Mail:hostmaster.securepoint.de
Serial:1435038684
Refresh:180
Retry:180
Expire:604800
TTL:180
num Entries:2


5. Url-Checks


show header:
Domainname Http-StatusredirectSec.G
• http://um.myfirewall.org/
93.216.142.45
301
https://um.myfirewall.org/
0.077
A
Server: nginx
Date: Tue, 12 Feb 2019 01:54:51 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://um.myfirewall.org/

• http://um.myfirewall.org/
2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69
-14

10.033
T
Timeout - The operation has timed out

• https://um.myfirewall.org/
93.216.142.45
200

4.077
B
Server: nginx
Date: Tue, 12 Feb 2019 01:55:04 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 621
Last-Modified: Sat, 05 Jan 2019 18:36:17 GMT
Connection: close
ETag: "5c30f921-26d"
Accept-Ranges: bytes

• https://um.myfirewall.org/
2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69
-14

10.030
T
Timeout - The operation has timed out

• http://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
93.216.142.45
301
https://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.080
A
Visible Content:
Server: nginx
Date: Tue, 12 Feb 2019 01:55:15 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69
-14

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

• https://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-14

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

6. Comments

Aname "um.myfirewall.org" is domain, public suffix is "myfirewall.org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
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: destination is https
Agood - only one version with Http-Status 200
Agood: one preferred version: non-www is preferred
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://um.myfirewall.org/ 93.216.142.45
301
https://um.myfirewall.org/
correct redirect http - https with the same domain name
Bhttps://um.myfirewall.org/ 93.216.142.45
200

Missing HSTS-Header
Khttp://um.myfirewall.org/ 93.216.142.45, Status 301

http://um.myfirewall.org/ 2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69, Status -14
configuration problem - different ip addresses with different status
Khttps://um.myfirewall.org/ 93.216.142.45, Status 200

https://um.myfirewall.org/ 2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69, Status -14
configuration problem - different ip addresses with different status
Khttp://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 93.216.142.45, Status 301

http://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69, Status -14
configuration problem - different ip addresses with different status
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: dyndns.securepoint.de: 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
http://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69
-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.
https://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-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://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:d3:bbbf:3e0:d621:22ff:fe7e:9d69, Status -14

http://um.myfirewall.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 93.216.142.45, Status 301
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. 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: 66924 milliseconds, 66.924 seconds


7. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
um.myfirewall.org
93.216.142.45
443
ok
Tls12
DiffieHellman
4096
Aes256
256
Sha384
not supported
ok
um.myfirewall.org
93.216.142.45
443
ok
Tls12
DiffieHellman
4096
Aes256
256
Sha384
not supported
ok


8. Certificates

1.
1.
CN=um.myfirewall.org
12.02.2019
13.05.2019
103 days expired
um.myfirewall.org - 1 entry
1.
1.
CN=um.myfirewall.org
12.02.2019

13.05.2019
103 days expired
um.myfirewall.org - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:035AF75C72A7781AE8A5BEA70464A897EF4F
Thumbprint:9A675D1DBB4025C6938B3009CAD703F7E0605AB4
SHA256 / Certificate:QQ8ULYtlt9pat91ngnK/nOP74NvTtO8o5O76YZtoxnc=
SHA256 hex / Cert (DANE * 0 1):410f142d8b65b7da5ab7dd678272bf9ce3fbe0dbd3b4ef28e4eefa619b68c677
SHA256 hex / PublicKey (DANE * 1 1):0b3722762306f4f53266cc6bce7573ffbd9d3e598eb30825ccf6d1edd1868cae
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 571 days


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
expires in 571 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 768 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 768 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no



9. Last Certificates - Certificate Transparency Log Check (BETA)

1. Source CertSpotter - active certificates

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.


2. Source crt.sh - old and new certificates, sometimes very slow.

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.


10. Html-Content - Entries (BETA - mixed content and other checks)

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
um.myfirewall.org
0

no CAA entry found
1
0
myfirewall.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
um.myfirewall.org

ok
1
0
_acme-challenge.um.myfirewall.org

Name Error - The domain name does not exist
1
0
_acme-challenge.um.myfirewall.org.um.myfirewall.org

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=639e631f-860b-4cee-92ed-de027350b6fc


Last Result: https://check-your-website.server-daten.de/?q=um.myfirewall.org - 2019-02-12 02:54:28


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

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