V

Connect failure - perhaps firewall

Checked:
15.05.2019 15:25:39


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
vm3.mcc.tu-berlin.de
A
130.149.22.34
Hostname: vm3.mcc.tu-berlin.de
yes
1
0

AAAA

yes


www.vm3.mcc.tu-berlin.de

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(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.06.2019, 00:00:00, Signature-Inception: 11.05.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
de
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: 28.05.2019, 05:00:00, Signature-Inception: 15.05.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 26298, Flags 256

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

1 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 30.05.2019, 12:00:00, Signature-Inception: 09.05.2019, 12:00:00, KeyTag 39227, Signer-Name: de

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

Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 39227, DigestType 2 and Digest "qrcwg7nvcOSl6UdppBisEuiH/DwIde8gbDRR3EC2xPo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
tu-berlin.de
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


mcc.tu-berlin.de
0 DS RR in the parent zone found

0 DNSKEY RR found


vm3.mcc.tu-berlin.de
0 DS RR in the parent zone found

0 DNSKEY RR found


www.vm3.mcc.tu-berlin.de
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.vm3.mcc.tu-berlin.de
  ns.tu-berlin.de

vm3.mcc.tu-berlin.de
  ns.tu-berlin.de
130.149.7.7

 
2001:638:809:7::7
mcc.tu-berlin.de
  ns.tu-berlin.de

tu-berlin.de
  dns-2.dfn.de


  dns-3.dfn.de


  ns.tu-berlin.de

de
  a.nic.de / ns-1.de.de8.bind


  f.nic.de / ns-2.de.de1.bind


  l.de.net / ns-1.de.fr1.bind


  n.de.net / s3.amx


  s.de.net / ns-2.de.de9.bind


  z.nic.de / ns-2.de.de8.bind


4. SOA-Entries


Domain:de
Primary:f.nic.de
Mail:its.denic.de
Serial:2019051561
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:tu-berlin.de
Primary:ns.tu-berlin.de
Mail:noc.tubit.tu-berlin.de
Serial:3150715709
Refresh:21600
Retry:3600
Expire:2592000
TTL:900
num Entries:3


Domain:mcc.tu-berlin.de
Primary:ns.tu-berlin.de
Mail:noc.tu-berlin.de
Serial:3180115018
Refresh:21600
Retry:3600
Expire:2592000
TTL:900
num Entries:1


Domain:vm3.mcc.tu-berlin.de
Primary:ns.tu-berlin.de
Mail:noc.tu-berlin.de
Serial:3180115018
Refresh:21600
Retry:3600
Expire:2592000
TTL:900
num Entries:2


5. Url-Checks

Domainname Http-StatusredirectSec.G
• http://vm3.mcc.tu-berlin.de/
130.149.22.34
-2

1.030
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 130.149.22.34:80

• https://vm3.mcc.tu-berlin.de/
130.149.22.34
-2

1.017
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 130.149.22.34:443

• http://vm3.mcc.tu-berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
130.149.22.34
-2

1.017
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 130.149.22.34:80
Visible Content:

6. Comments

Aname "vm3.mcc.tu-berlin.de" is subdomain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
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
Vhttp://vm3.mcc.tu-berlin.de/ 130.149.22.34
-2

connect failure - perhaps firewall
Vhttps://vm3.mcc.tu-berlin.de/ 130.149.22.34
-2

connect failure - perhaps firewall
Vhttp://vm3.mcc.tu-berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 130.149.22.34
-2

connect failure - perhaps firewall
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: n.de.net: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (s3.amx). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns.tu-berlin.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
http://vm3.mcc.tu-berlin.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 130.149.22.34
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.
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: 21530 milliseconds, 21.530 seconds


7. Connections

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 (BETA)

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
912930199
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-05-15 07:53:42
2019-08-13 07:53:42
vm3.mcc.tu-berlin.de - 1 entries



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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1473237609
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-05-15 05:53:42
2019-08-13 05:53:42
vm3.mcc.tu-berlin.de
1 entries



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
vm3.mcc.tu-berlin.de
0

no CAA entry found
1
0
mcc.tu-berlin.de
0

no CAA entry found
1
0
tu-berlin.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
vm3.mcc.tu-berlin.de

ok
1
0
_acme-challenge.vm3.mcc.tu-berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.vm3.mcc.tu-berlin.de.mcc.tu-berlin.de

Name Error - The domain name does not exist
1
0
_acme-challenge.vm3.mcc.tu-berlin.de.vm3.mcc.tu-berlin.de

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=f13655c6-ec41-415f-911b-35f05003722b


Last Result: https://check-your-website.server-daten.de/?q=vm3.mcc.tu-berlin.de - 2019-05-15 15:25:39


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

<a href="https://check-your-website.server-daten.de/?q=vm3.mcc.tu-berlin.de" target="_blank">Check this Site: vm3.mcc.tu-berlin.de</a>