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



V

Connect failure - perhaps firewall

Checked:
18.08.2019 16:45:17


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
thetradinghall.com
A
83.166.144.177
Geneva/Switzerland (CH) - Infomaniak Network SA
Hostname: web1.sportsdailynow.com
yes
1
0

AAAA
2001:1600:4:8:f816:3eff:fe2e:4f73
Carouge/Geneva/Switzerland (CH) - Infomaniak Network SA

yes


www.thetradinghall.com

Name Error
yes
1
0


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



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.08.2019, 05:00:00 +, Signature-Inception: 18.08.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.08.2019, 18:25:33 +, Signature-Inception: 10.08.2019, 18:20:33 +, KeyTag 30909, Signer-Name: com



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



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

Zone: thetradinghall.com
thetradinghall.com
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 "5a4ja9lv2nbi55m0pk9cbbd54iearn7q" between the hashed NSEC3-owner "5a4ilaroin5aevocseba9ajd0m9e0ojg" and the hashed NextOwner "5a4lo9b29sd492h63fsq9rh6fi1p54bp". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 5a4ilaroin5aevocseba9ajd0m9e0ojg.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 23.08.2019, 04:23:12 +, Signature-Inception: 16.08.2019, 03:13:12 +, KeyTag 17708, Signer-Name: com



1 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 25176, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner thetradinghall.com., Algorithm: 13, 2 Labels, original TTL: 10800 sec, Signature-expiration: 29.08.2019, 00:00:00 +, Signature-Inception: 08.08.2019, 00:00:00 +, KeyTag 25176, Signer-Name: thetradinghall.com



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



Error: DNSKEY 25176 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



RRSIG Type 1 validates the A - Result: 83.166.144.177
Validated: RRSIG-Owner thetradinghall.com., Algorithm: 13, 2 Labels, original TTL: 10800 sec, Signature-expiration: 29.08.2019, 00:00:00 +, Signature-Inception: 08.08.2019, 00:00:00 +, KeyTag 25176, Signer-Name: thetradinghall.com



RRSIG Type 28 validates the AAAA - Result: 2001:1600:0004:0008:F816:3EFF:FE2E:4F73
Validated: RRSIG-Owner thetradinghall.com., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 29.08.2019, 00:00:00 +, Signature-Inception: 08.08.2019, 00:00:00 +, KeyTag 25176, Signer-Name: thetradinghall.com



RRSIG Type 50, expiration 2019-08-29 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CNAME RR.
Bitmap: A, NS, SOA, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2019-08-29 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TXT RR.
Bitmap: A, NS, SOA, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2019-08-29 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TLSA RR.
Bitmap: A, NS, SOA, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2019-08-29 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CAA RR.
Bitmap: A, NS, SOA, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS

Zone: www.thetradinghall.com
www.thetradinghall.com
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 "fubhkk07ut96dgput2befpkuqd9sdjqv" between the hashed NSEC3-owner "fubhkk07ut96dgput2befpkuqd9sdjqu" and the hashed NextOwner "fubhkk07ut96dgput2befpkuqd9sdjr0". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner fubhkk07ut96dgput2befpkuqd9sdjqu.thetradinghall.com., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 29.08.2019, 00:00:00 +, Signature-Inception: 08.08.2019, 00:00:00 +, KeyTag 25176, Signer-Name: thetradinghall.com


3. Name Servers

DomainNameserverNS-IP
www.thetradinghall.com
  ns1.gandi.net

thetradinghall.com
  ns-118-a.gandi.net / node-berlin1
173.246.100.119
Ashburn/Virginia/United States (US) - Gandi SAS


 
2001:4b98:aaaa::77
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar


  ns-209-c.gandi.net / node-berlin1
217.70.187.210
Newark/New Jersey/United States (US) - GANDI is an ICANN accredited registrar


 
2604:3400:aaac::d2
Ashburn/Virginia/United States (US) - Gandi SAS


  ns-217-b.gandi.net / node-berlin1
213.167.230.218
Newark/New Jersey/United States (US) - Gandi SAS


 
2001:4b98:aaab::da
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


T  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:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1566139500
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:12


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


Domain:thetradinghall.com
Zone-Name:
Primary:ns1.gandi.net
Mail:hostmaster.gandi.net
Serial:1565827200
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:6


Domain:www.thetradinghall.com
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://thetradinghall.com/
83.166.144.177
200

0.057
H
Server: nginx/1.14.2
Date: Sun, 18 Aug 2019 14:45:57 GMT
Content-Type: text/html
Content-Length: 3711
Last-Modified: Fri, 16 Aug 2019 16:12:27 GMT
Connection: close
ETag: "5d56d5eb-e7f"
Accept-Ranges: bytes

• http://thetradinghall.com/
2001:1600:4:8:f816:3eff:fe2e:4f73
200

0.060
H
Server: nginx/1.14.2
Date: Sun, 18 Aug 2019 14:45:57 GMT
Content-Type: text/html
Content-Length: 3711
Last-Modified: Fri, 16 Aug 2019 16:12:27 GMT
Connection: close
ETag: "5d56d5eb-e7f"
Accept-Ranges: bytes

• https://thetradinghall.com/
83.166.144.177
-2

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

• https://thetradinghall.com/
2001:1600:4:8:f816:3eff:fe2e:4f73
-2

1.090
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it [2001:1600:4:8:f816:3eff:fe2e:4f73]:443

• http://thetradinghall.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
83.166.144.177
200

0.053

Visible Content:
Server: nginx/1.14.2
Date: Sun, 18 Aug 2019 14:45:59 GMT
Content-Type: text/html
Content-Length: 3711
Last-Modified: Fri, 16 Aug 2019 16:12:27 GMT
Connection: close
ETag: "5d56d5eb-e7f"
Accept-Ranges: bytes

• http://thetradinghall.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:1600:4:8:f816:3eff:fe2e:4f73
200

0.060

Visible Content:
Server: nginx/1.14.2
Date: Sun, 18 Aug 2019 14:46:00 GMT
Content-Type: text/html
Content-Length: 3711
Last-Modified: Fri, 16 Aug 2019 16:12:27 GMT
Connection: close
ETag: "5d56d5eb-e7f"
Accept-Ranges: bytes

7. Comments


1. General Results, most used to calculate the result

Aname "thetradinghall.com" is domain, public suffix is "com", 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
AExcellent: Domain is in the Google-Preload-List
AExcellent: Domain is in the Mozilla/Firefox-Preload-List
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://thetradinghall.com/ 83.166.144.177


Url with incomplete Content-Type - header - missing charset
http://thetradinghall.com/ 2001:1600:4:8:f816:3eff:fe2e:4f73


Url with incomplete Content-Type - header - missing charset
http://thetradinghall.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 83.166.144.177


Url with incomplete Content-Type - header - missing charset
http://thetradinghall.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1600:4:8:f816:3eff:fe2e:4f73


Url with incomplete Content-Type - header - missing charset
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Vhttps://thetradinghall.com/ 83.166.144.177
-2

connect failure - perhaps firewall
Vhttps://thetradinghall.com/ 2001:1600:4:8:f816:3eff:fe2e:4f73
-2

connect failure - perhaps firewall

2. DNS- and NameServer - Checks

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
XNameserver Timeout checking EDNS512: g.gtld-servers.net
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: f.gtld-servers.net: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.gandi.net: 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://thetradinghall.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 83.166.144.177
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://thetradinghall.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1600:4:8:f816:3eff:fe2e:4f73
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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: 54640 milliseconds, 54.640 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

Summary

No data found or small Code-update

Details

Small Code Update - wait one minute


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
thetradinghall.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
thetradinghall.com

ok
1
0
_acme-challenge.thetradinghall.com

Name Error - The domain name does not exist
1
0
_acme-challenge.thetradinghall.com.thetradinghall.com

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 open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=e5d88db3-c52b-4348-bb7c-fff17ae56a6d


Last Result: https://check-your-website.server-daten.de/?q=thetradinghall.com - 2019-08-18 16:45:17


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

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

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