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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
07.04.2019 21:10:52

Older results

V - 05.04.2019 20:08:49

V - 05.04.2019 19:50:25

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
gauderskins.trade	A	46.101.25.252 No Hostname found	yes	1	0
	AAAA		yes
www.gauderskins.trade	A	46.101.25.252 No Hostname found	yes	1	0
	AAAA		yes

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


	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


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


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner trade., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.04.2019, 17:00:00 +, Signature-Inception: 07.04.2019, 16: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


	6 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 2476, Flags 256


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


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


	Public Key with Algorithm 8, KeyTag 25899, Flags 256


	Public Key with Algorithm 8, KeyTag 37306, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner trade., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 07.05.2019, 04:34:56 +, Signature-Inception: 07.04.2019, 03:40:00 +, KeyTag 20971, Signer-Name: trade


	RRSIG-Owner trade., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 07.05.2019, 04:34:56 +, Signature-Inception: 07.04.2019, 03:40:00 +, KeyTag 25899, Signer-Name: trade


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


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20971, DigestType 1 and Digest "u6WMST/fkhVCPFuZMXxD+T4WymA=" 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 8, KeyTag 20971, DigestType 2 and Digest "4u/nrNdgIiphv0TGNqS3u/FVluY8z1mlndqWnD/z6rU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: gauderskins.trade
gauderskins.trade	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.gauderskins.trade
www.gauderskins.trade	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.gauderskins.trade	• ns.datacenter.no		•
gauderskins.trade	• ns.datacenter.no	81.27.32.80	•
	• ns2.datacenter.no	212.62.224.190	•
trade	• ns1.dns.nic.trade		•
	• ns2.dns.nic.trade		•
	• ns3.dns.nic.trade		•
	• ns4.dns.nic.trade		•
	• ns5.dns.nic.trade		•
	• ns6.dns.nic.trade		•

4. SOA-Entries

Domain:	trade
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	trade
Zone-Name:
Primary:	ns1.dns.nic.trade
Mail:	hostmaster.neustar.biz
Serial:	1554663640
Refresh:	900
Retry:	900
Expire:	604800
TTL:	60
num Entries:	5

Domain:	gauderskins.trade
Zone-Name:
Primary:	ns.datacenter.no
Mail:	hostmaster.gauderskins.trade
Serial:	1554662793
Refresh:	16384
Retry:	2048
Expire:	1048576
TTL:	2560
num Entries:	2

Domain:	www.gauderskins.trade
Zone-Name:
Primary:	ns.datacenter.no
Mail:	hostmaster.gauderskins.trade
Serial:	1554662793
Refresh:	16384
Retry:	2048
Expire:	1048576
TTL:	2560
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

show header:

Domainname	Http-Status	Sec.	G
• http://gauderskins.trade/ 46.101.25.252	200	0.090	H
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Sun, 07 Apr 2019 12:26:41 GMT
ETag: W/"7111-169f7c3d997"
Content-Type: text/html; charset=UTF-8
Content-Length: 28945
set-cookie: csg0trade=s%3ALYEwzrkbYEVc6dbq0E5YMmxRh-WAjEqD.TXRSDc6vhANXYWtIV6gqa0C1yaYrO0Z6NXHJ7bDMtWg; Path=/; HttpOnly
Date: Sun, 07 Apr 2019 19:11:11 GMT
Connection: close

• http://www.gauderskins.trade/ 46.101.25.252	200	0.090	H
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Sun, 07 Apr 2019 12:26:41 GMT
ETag: W/"7111-169f7c3d997"
Content-Type: text/html; charset=UTF-8
Content-Length: 28945
set-cookie: csg0trade=s%3AwZNUS6y3hM1QRRMj-eI7NlXOvyXZKvqP.9PdyHJXOklkUb5DPNakkXjqrbm1hwoHVM%2FDNwbtAi7Q; Path=/; HttpOnly
Date: Sun, 07 Apr 2019 19:11:12 GMT
Connection: close

• https://gauderskins.trade/ 46.101.25.252	-2	1.050	V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 46.101.25.252:443

• https://www.gauderskins.trade/ 46.101.25.252	-2	1.073	V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 46.101.25.252:443

• http://gauderskins.trade/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.25.252	404	0.054	A
Not Found
Visible Content:
X-Powered-By: Express
Content-Security-Policy: default-src 'self'
X-Content-Type-Options: nosniff
Content-Type: text/html; charset=utf-8
Content-Length: 208
set-cookie: csg0trade=s%3Aw8DDQ5FBa3W6dKJpa94VzkDCozTd1PCr.TuSAYbhSBzdo54CUsAl%2BQEtxFCfY4%2BTSZCb%2Bhh2IryI; Path=/; HttpOnly
Date: Sun, 07 Apr 2019 19:11:14 GMT
Connection: close

• http://www.gauderskins.trade/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.25.252	404	0.047	A
Not Found
Visible Content:
X-Powered-By: Express
Content-Security-Policy: default-src 'self'
X-Content-Type-Options: nosniff
Content-Type: text/html; charset=utf-8
Content-Length: 208
set-cookie: csg0trade=s%3AVXu-YDebN1RPPOUTH0Nm56yAHIkt1z0R.flHTUfkYG8%2FEV5WNa60OElNK5d4znhfZ1K5296jgHA8; Path=/; HttpOnly
Date: Sun, 07 Apr 2019 19:11:14 GMT
Connection: close

7. Comments

	1. General Results, most used to calculate the result
A	name "gauderskins.trade" is domain, public suffix is "trade", top-level-domain-type is "generic", tld-manager is "Elite Registry Limited"
A	Good: All ip addresses are public addresses
A	Good: No asked Authoritative Name Server had a timeout
A	Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
C	Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
H	Fatal error: No https - result with http-status 200, no encryption
H	Fatal 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.
V	https://gauderskins.trade/ 46.101.25.252	-2	Connect failure - perhaps firewall
V	https://www.gauderskins.trade/ 46.101.25.252	-2	Connect failure - perhaps firewall
	2. Header-Checks
	3. DNS- and NameServer - Checks
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
X	Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns.datacenter.no
X	Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.datacenter.no
	Nameserver doesn't pass all EDNS-Checks: ns.datacenter.no: 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.
	Nameserver doesn't pass all EDNS-Checks: ns.datacenter.no / 81.27.32.80: 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.
	Nameserver doesn't pass all EDNS-Checks: ns2.datacenter.no / 212.62.224.190: 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.
A	Good: 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
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Good: 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
A	Duration: 21710 milliseconds, 21.710 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

Small Code Update - wait one minute

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

Domainname	Value	∑ Queries
www.gauderskins.trade	no CAA entry found	1
gauderskins.trade	no CAA entry found	1
trade	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
gauderskins.trade	google-site-verification=fA_-NZVxymS1eb9k-NBrEcrx2SLfUBqKW5yzn2osm_s	ok	1
gauderskins.trade	v=spf1 include:spf.webhuset.no -all	ok	1
www.gauderskins.trade	google-site-verification=fA_-NZVxymS1eb9k-NBrEcrx2SLfUBqKW5yzn2osm_s	ok	1
_acme-challenge.gauderskins.trade	HYI7rs4kOY3Zma4GGvzFcpAY4m8Woco7tj17y74RgwM	looks good, correct length, correct characters	1
_acme-challenge.www.gauderskins.trade		Name Error - The domain name does not exist	1
_acme-challenge.gauderskins.trade.gauderskins.trade		Name Error - The domain name does not exist	1
_acme-challenge.www.gauderskins.trade.www.gauderskins.trade		Name Error - The domain name does not exist	1

15. DomainService - Entries

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=84425cf2-6430-4afe-8fd8-a4c5291bcdee

Last Result: https://check-your-website.server-daten.de/?q=gauderskins.trade - 2022-01-29 18:51:04

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

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

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