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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
27.01.2019 11:23:43

Older results

A - 27.01.2019 11:15:20

W - 27.01.2019 11:07:16

T - 27.01.2019 10:54:44

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
yvonne.inpersona.dk	A	83.92.5.233 Hostname: 83-92-5-233-cable.dk.customer.tdc.net	yes	1	0
	AAAA		yes
www.yvonne.inpersona.dk		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 16749, Flags 256


	Public Key with Algorithm 8, KeyTag 19164, Flags 385


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2019, 00:00:00 +, Signature-Inception: 21.01.2019, 00:00:00 +, KeyTag 19164, Signer-Name: (root)


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2019, 00:00:00 +, Signature-Inception: 21.01.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


	• 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: dk
dk	1 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner dk., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.02.2019, 05:00:00 +, Signature-Inception: 27.01.2019, 04:00:00 +, KeyTag 16749, Signer-Name: (root)


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 47796, Flags 256


	Public Key with Algorithm 8, KeyTag 57799, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner dk., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.02.2019, 06:38:08 +, Signature-Inception: 26.01.2019, 00:03:37 +, KeyTag 32195, Signer-Name: dk


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


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

Zone: inpersona.dk
inpersona.dk	1 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner inpersona.dk., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 21.02.2019, 15:02:27 +, Signature-Inception: 24.01.2019, 09:03:42 +, KeyTag 47796, Signer-Name: dk


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


	2 DNSKEY RR found


	Public Key with Algorithm 5, KeyTag 49459, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 5, KeyTag 63591, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner inpersona.dk., Algorithm: 5, 2 Labels, original TTL: 43200 sec, Signature-expiration: 24.02.2019, 23:35:25 +, Signature-Inception: 25.01.2019, 23:35:25 +, KeyTag 49459, Signer-Name: inpersona.dk


	RRSIG-Owner inpersona.dk., Algorithm: 5, 2 Labels, original TTL: 43200 sec, Signature-expiration: 24.02.2019, 23:35:25 +, Signature-Inception: 25.01.2019, 23:35:25 +, KeyTag 63591, Signer-Name: inpersona.dk


	• Status: Good - Algorithmus 5 and DNSKEY with KeyTag 49459 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 5 and DNSKEY with KeyTag 63591 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 5, KeyTag 49459, DigestType 1 and Digest "1ABXcCB4DIv0Q5vIBIJDE5A6+8w=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: yvonne.inpersona.dk
yvonne.inpersona.dk	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.yvonne.inpersona.dk
www.yvonne.inpersona.dk	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.yvonne.inpersona.dk	• ns1.gratisdns.dk
yvonne.inpersona.dk	• ns1.gratisdns.dk
inpersona.dk	• ns1.gratisdns.dk
	• ns2.gratisdns.dk
	• ns3.gratisdns.dk
	• ns4.gratisdns.dk
	• ns5.gratisdns.dk
dk	• a.nic.dk
	• b.nic.dk
	• c.nic.dk
	• l.nic.dk
	• p.nic.dk
	• s.nic.dk

4. SOA-Entries

No SOA informations found. The feature is new (startet 2019-02-05), so recheck this domain.

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://yvonne.inpersona.dk/ 83.92.5.233	301	https://yvonne.inpersona.dk/	0.086	A
Date: Sun, 27 Jan 2019 10:23:53 GMT
Server: Apache
Location: https://yvonne.inpersona.dk/
Content-Length: 236
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://yvonne.inpersona.dk/ 83.92.5.233	200		2.670	A
Date: Sun, 27 Jan 2019 10:23:54 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains
Vary: Accept-Encoding
Content-Length: 327
Connection: close
Content-Type: text/html; charset=UTF-8

• http://yvonne.inpersona.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 83.92.5.233	301	https://yvonne.inpersona.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	0.083	A
Visible Content:
Date: Sun, 27 Jan 2019 10:23:56 GMT
Server: Apache
Location: https://yvonne.inpersona.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 305
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://yvonne.inpersona.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404		1.846	A
Not Found
Visible Content:
Date: Sun, 27 Jan 2019 10:23:56 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Length: 337
Connection: close
Content-Type: text/html; charset=iso-8859-1

7. Comments

	1. General Results, most used to calculate the result
A	name "yvonne.inpersona.dk" is subdomain, public suffix is "dk", top-level-domain-type is "country-code", Country is Denmark, tld-manager is "Dansk Internet Forum"
A	Good: All ip addresses are public addresses
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: non-www is preferred
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS max-age is long enough, 31536000 seconds = 365 days
A	Good: HSTS has includeSubdomains - directive
A	Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
A	http://yvonne.inpersona.dk/ 83.92.5.233	301	https://yvonne.inpersona.dk/	Correct redirect http - https with the same domain name
	2. Header-Checks
	3. DNS- and NameServer - Checks
A	Good: Nameserver supports TCP connections: 1 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 1 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
	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
	https://yvonne.inpersona.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	1.846 seconds	Warning: 404 needs more then one second
A	Duration: 12137 milliseconds, 12.137 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

yvonne.inpersona.dk

83.92.5.233

443

Tls12

DiffieHellman

4096

Aes256

256

Sha384

not supported

yvonne.inpersona.dk

83.92.5.233

443

Tls12

DiffieHellman

4096

Aes256

256

Sha384

not supported

no Tls.1.2
no Tls.1.1
no Tls.1.0

9. Certificates

CN=yvonne.inpersona.dk

25.01.2019

26.04.2019
2208 days expired

yvonne.inpersona.dk - 1 entry

CN=yvonne.inpersona.dk

25.01.2019

26.04.2019
2208 days expired

yvonne.inpersona.dk - 1 entry

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0321422FD87B3F136BB074BDD73CADCD15B4
Thumbprint:	AF8E98CC993D6022A358DD75633598E845980C39
SHA256 / Certificate:	Gg8/d0qXj3FF+Spf0kuNKGPUu38UNRB+u9pDULNo130=
SHA256 hex / Cert (DANE * 0 1):	1a0f3f774a978f7145f92a5fd24b8d2863d4bb7f1435107ebbda4350b368d77d
SHA256 hex / PublicKey (DANE * 1 1):	cc84054d4136d5ba1fc0dd776791324ac3b6235cafc1239ae4ea486451d20bd2
SHA256 hex / Subject Public Key Information (SPKI):	cc84054d4136d5ba1fc0dd776791324ac3b6235cafc1239ae4ea486451d20bd2
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1517 days expired

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1517 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0A0141420000015385736A0B85ECA708
Thumbprint:	E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:	JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):	25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1320 days expired

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1320 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	44AFB080D6A327BA893039862EF8406B
Thumbprint:	DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:	BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

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

Domainname	Value	∑ Queries
yvonne.inpersona.dk	no CAA entry found	1
inpersona.dk	no CAA entry found	1
dk	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
yvonne.inpersona.dk	ok	1
_acme-challenge.yvonne.inpersona.dk	Name Error - The domain name does not exist	1
_acme-challenge.yvonne.inpersona.dk.yvonne.inpersona.dk	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. 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=cd721068-3889-4703-a8f4-c3937e01bdaf

Last Result: https://check-your-website.server-daten.de/?q=yvonne.inpersona.dk - 2019-01-27 11:23:43

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

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