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



V

Connect failure - perhaps firewall

Checked:
25.06.2019 16:34:45


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
elberthome.dnshome.de
A
84.152.247.218
Uettingen/Bavaria/DE
Hostname: p5498f7da.dip0.t-ipconnect.de
yes
1
0

AAAA

yes


www.elberthome.dnshome.de

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

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



Status: Valid because published



3 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



Public Key with Algorithm 8, KeyTag 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.07.2019, 05:00:00 +, Signature-Inception: 25.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 22771, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 11.07.2019, 12:00:00 +, Signature-Inception: 20.06.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

Zone: dnshome.de
dnshome.de
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner dnshome.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2019, 13:01:15 +, Signature-Inception: 25.06.2019, 13:01:15 +, KeyTag 22771, Signer-Name: de



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



1 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 64035, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner dnshome.de., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 04.07.2019, 00:00:00 +, Signature-Inception: 13.06.2019, 00:00:00 +, KeyTag 64035, Signer-Name: dnshome.de



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 64035 used to validate the DNSKEY RRSet



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

Zone: elberthome.dnshome.de
elberthome.dnshome.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 query name "84hv0dl18cokic3bflfj9srpe693nrsa" between the hashed NSEC3-owner "84hv0dl18cokic3bflfj9srpe693nrsa" and the hashed NextOwner "84hv0dl18cokic3bflfj9srpe693nrsb". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 84hv0dl18cokic3bflfj9srpe693nrsa.dnshome.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.07.2019, 00:00:00 +, Signature-Inception: 13.06.2019, 00:00:00 +, KeyTag 64035, Signer-Name: dnshome.de



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 84.152.247.218
Validated: RRSIG-Owner elberthome.dnshome.de., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 04.07.2019, 00:00:00 +, Signature-Inception: 13.06.2019, 00:00:00 +, KeyTag 64035, Signer-Name: dnshome.de



RRSIG Type 50, expiration 2019-07-04 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CNAME RR.
Bitmap: A, RRSIG



RRSIG Type 50, expiration 2019-07-04 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TXT RR.
Bitmap: A, RRSIG



RRSIG Type 50, expiration 2019-07-04 00:00:00 + validates the NSEC3 RR that proves the not-existence of the AAAA RR.
Bitmap: A, RRSIG



RRSIG Type 50, expiration 2019-07-04 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TLSA RR.
Bitmap: No Bitmap?



RRSIG Type 50, expiration 2019-07-04 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TLSA RR.
Bitmap: A, RRSIG



RRSIG Type 50, expiration 2019-07-04 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CAA RR.
Bitmap: A, RRSIG

Zone: www.elberthome.dnshome.de
www.elberthome.dnshome.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 query name "3a7q83hncinc49umdlvt5u0iph2qhdg4" between the hashed NSEC3-owner "3a7q83hncinc49umdlvt5u0iph2qhdg3" and the hashed NextOwner "3a7q83hncinc49umdlvt5u0iph2qhdg5". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 3a7q83hncinc49umdlvt5u0iph2qhdg3.dnshome.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.07.2019, 00:00:00 +, Signature-Inception: 13.06.2019, 00:00:00 +, KeyTag 64035, Signer-Name: dnshome.de


3. Name Servers

DomainNameserverNS-IP
www.elberthome.dnshome.de
  ns1.dnshome.de

elberthome.dnshome.de
  ns1.dnshome.de / ns1.dnshome.de
185.233.106.232
/DE


 
2a03:4000:24:688::6e73:31
Karlsruhe/Baden-Wurttemberg/DE

dnshome.de
  ns1.dnshome.de / ns1.dnshome.de


  ns2.dnshome.de / ns2.dnshome.de

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


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


  l.de.net / ns-2.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
Zone-Name:
Primary:f.nic.de
Mail:its.denic.de
Serial:2019062565
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:dnshome.de
Zone-Name:
Primary:ns1.dnshome.de
Mail:hostmaster.dnshome.de
Serial:2019030501
Refresh:14400
Retry:3600
Expire:604800
TTL:3600
num Entries:2


Domain:elberthome.dnshome.de
Zone-Name:
Primary:ns1.dnshome.de
Mail:hostmaster.dnshome.de
Serial:2019030501
Refresh:14400
Retry:3600
Expire:604800
TTL:3600
num Entries:2


Domain:www.elberthome.dnshome.de
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://elberthome.dnshome.de/
84.152.247.218
-2

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

• https://elberthome.dnshome.de/
84.152.247.218
-2

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

• http://elberthome.dnshome.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
84.152.247.218
-14

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

7. Comments


1. General Results, most used to calculate the result

Aname "elberthome.dnshome.de" is domain, public suffix is "dnshome.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://elberthome.dnshome.de/ 84.152.247.218
-2

connect failure - perhaps firewall
Vhttps://elberthome.dnshome.de/ 84.152.247.218
-2

connect failure - perhaps firewall

2. DNS- and NameServer - Checks

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: ns1.dnshome.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 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

http://elberthome.dnshome.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 84.152.247.218
-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: 33800 milliseconds, 33.800 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)

Small Code Update - wait one minute


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months 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:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
elberthome.dnshome.de
0

no CAA entry found
1
0
dnshome.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
elberthome.dnshome.de

ok
1
0
_acme-challenge.elberthome.dnshome.de

Name Error - The domain name does not exist
1
0
_acme-challenge.elberthome.dnshome.de.elberthome.dnshome.de

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)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

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=3b81505c-95b3-4659-9f23-a46b2bc227ef


Last Result: https://check-your-website.server-daten.de/?q=elberthome.dnshome.de - 2019-06-25 16:34:45


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro