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


 

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bgcamp.de
A
88.99.144.208
Falkenstein/Saxony/Germany (DE) - Hetzner
Hostname: bgcamp.bilsteingroup.com
yes
1
0

AAAA

yes


www.bgcamp.de
A
88.99.144.208
Falkenstein/Saxony/Germany (DE) - Hetzner
Hostname: bgcamp.bilsteingroup.com
yes
1
0

AAAA

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2019, 00:00:00 +, Signature-Inception: 21.10.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: 05.11.2019, 05:00:00 +, Signature-Inception: 23.10.2019, 04:00:00 +, KeyTag 22545, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 26008, Flags 256






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






Public Key with Algorithm 8, KeyTag 44385, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

bgcamp.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 "5uns0khai3smovpkc8ofc8tltu67cf1d" between the hashed NSEC3-owner "5uno6lso5pbrbfit68jb5lj57mkravlp" and the hashed NextOwner "5uo2prpodn8t6i8hvbvum9u9n3mtek7e". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 5uno6lso5pbrbfit68jb5lj57mkravlp.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 30.10.2019, 11:01:05 +, Signature-Inception: 23.10.2019, 11:01:05 +, KeyTag 26008, Signer-Name: de






0 DNSKEY RR found









Zone: www.bgcamp.de

www.bgcamp.de
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.bgcamp.de
  ns1.first-ns.de

bgcamp.de
  ns1.first-ns.de
213.239.242.238
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH


 
2a01:4f8:0:a101::a:1
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH


  robotns2.second-ns.de
213.133.105.6
Nuremberg/Bavaria/Germany (DE) - Hetzner


 
2a01:4f8:d0a:2004::2
Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH


  robotns3.second-ns.com
193.47.99.3
Düsseldorf/North Rhine-Westphalia/Germany (DE) - myLoc managed IT AG


 
2001:67c:192c::add:a3
Düsseldorf/North Rhine-Westphalia/Germany (DE) - myLoc managed IT AG

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


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


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


  n.de.net / s3.tok


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


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

 

4. SOA-Entries


Domain:de
Zone-Name:
Primary:f.nic.de
Mail:its.denic.de
Serial:2019102353
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:1


Domain:de
Zone-Name:
Primary:f.nic.de
Mail:its.denic.de
Serial:2019102357
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:5


Domain:bgcamp.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:bgcamp.de
Zone-Name:
Primary:ns1.first-ns.de
Mail:postmaster.robot.first-ns.de
Serial:2019102300
Refresh:86400
Retry:10800
Expire:3600000
TTL:86400
num Entries:5


Domain:www.bgcamp.de
Zone-Name:
Primary:ns1.first-ns.de
Mail:postmaster.robot.first-ns.de
Serial:2019102300
Refresh:86400
Retry:10800
Expire:3600000
TTL:86400
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://bgcamp.de/
88.99.144.208
-14


10.046
T
Timeout - The operation has timed out

• http://www.bgcamp.de/
88.99.144.208
-14


10.040
T
Timeout - The operation has timed out

• https://bgcamp.de/
88.99.144.208
-14


10.030
T
Timeout - The operation has timed out

• https://www.bgcamp.de/
88.99.144.208
-14


10.116
T
Timeout - The operation has timed out

• http://bgcamp.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
88.99.144.208
-14


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

• http://www.bgcamp.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
88.99.144.208
-14


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

 

7. Comments


1. General Results, most used to calculate the result

Aname "bgcamp.de" is domain, 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
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. Header-Checks


3. DNS- and NameServer - Checks

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.first-ns.de,robotns2.second-ns.de,robotns3.second-ns.com
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
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.

4. Content- and Performance-critical Checks

http://bgcamp.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.99.144.208
-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://www.bgcamp.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.99.144.208
-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: 110427 milliseconds, 110.427 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" > 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. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. 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.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.bgcamp.de
0

no CAA entry found
1
0
bgcamp.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bgcamp.de

ok
1
0
www.bgcamp.de

ok
1
0
_acme-challenge.bgcamp.de
qGKsKp1Ug9cnOhbRIfzO0lK8Y4YpdIEj2dHJCc4Vdew
looks good, correct length, correct characters
1
0
_acme-challenge.www.bgcamp.de

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

Name Error - The domain name does not exist
1
0
_acme-challenge.www.bgcamp.de.bgcamp.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.bgcamp.de.www.bgcamp.de

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=130e2294-e601-4670-b2fb-1205ee562ab9

 

Last Result: https://check-your-website.server-daten.de/?q=bgcamp.de - 2019-10-23 14:27:47

 

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

 

<a href="https://check-your-website.server-daten.de/?q=bgcamp.de" target="_blank">Check this Site: bgcamp.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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=bgcamp.de