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

0 in Queue, 1 of max. 8 Checks (13:47:39)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A+

 

Top configuration, no warnings +Preload

 

Checked:
20.06.2021 20:50:44

 

Older results

 

C - 20.06.2021 20:40:39
X - 20.06.2021 08:37:37
X - 20.06.2021 07:11:58
X - 20.06.2021 06:14:11
X - 20.06.2021 01:03:18

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
nightquest.dev
A
73.159.106.131
Bristol/Connecticut/United States (US) - Comcast Cable Communications, LLC
Hostname: c-73-159-106-131.hsd1.ma.comcast.net
yes
1
0

AAAA

yes


www.nightquest.dev
A
73.159.106.131
Bristol/Connecticut/United States (US) - Comcast Cable Communications, LLC
Hostname: c-73-159-106-131.hsd1.ma.comcast.net
yes
1
0

AAAA

yes


*.nightquest.dev
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






• Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 14631, Flags 256






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






Public Key with Algorithm 8, KeyTag 26838, 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.2021, 00:00:00 +, Signature-Inception: 20.06.2021, 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: dev

dev
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=






1 RRSIG RR to validate DS RR found






RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.07.2021, 17:00:00 +, Signature-Inception: 20.06.2021, 16:00:00 +, KeyTag 14631, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 48574, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 08.07.2021, 15:19:06 +, Signature-Inception: 16.06.2021, 15:19:06 +, KeyTag 60074, Signer-Name: dev






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






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



Zone: nightquest.dev

nightquest.dev
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 28390, DigestType 2 and Digest HeVFnY2FIR+v/k9nZBRSYMXbJgv/A0vgoAkxnxDkzRA=






1 RRSIG RR to validate DS RR found






RRSIG-Owner nightquest.dev., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.07.2021, 15:19:06 +, Signature-Inception: 16.06.2021, 15:19:06 +, KeyTag 48574, Signer-Name: dev






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 57379, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner nightquest.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 28390, Signer-Name: nightquest.dev






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






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






RRSIG Type 1 validates the A - Result: 73.159.106.131
Validated: RRSIG-Owner nightquest.dev., Algorithm: 8, 2 Labels, original TTL: 60 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "cdjpoj0olt2gqoooaaoojldaeo1m75s3" equal the hashed NSEC3-owner "cdjpoj0olt2gqoooaaoojldaeo1m75s3" and the hashed NextOwner "p2f4pcof1cd0k96bn3po90ab3scm0r8n". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner cdjpoj0olt2gqoooaaoojldaeo1m75s3.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "cdjpoj0olt2gqoooaaoojldaeo1m75s3" equal the hashed NSEC3-owner "cdjpoj0olt2gqoooaaoojldaeo1m75s3" and the hashed NextOwner "p2f4pcof1cd0k96bn3po90ab3scm0r8n". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner cdjpoj0olt2gqoooaaoojldaeo1m75s3.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "cdjpoj0olt2gqoooaaoojldaeo1m75s3" equal the hashed NSEC3-owner "cdjpoj0olt2gqoooaaoojldaeo1m75s3" and the hashed NextOwner "p2f4pcof1cd0k96bn3po90ab3scm0r8n". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner cdjpoj0olt2gqoooaaoojldaeo1m75s3.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.nightquest.dev) sends a valid NSEC3 RR as result with the hashed owner name "cdjpoj0olt2gqoooaaoojldaeo1m75s3" (unhashed: nightquest.dev). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner cdjpoj0olt2gqoooaaoojldaeo1m75s3.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "86bdf61tsp787v05ruh02ib5t76dg9kr" (unhashed: _tcp.nightquest.dev) with the owner "5ud3ohks9c5ualn3rvdpca7ius0m9n6d" and the NextOwner "apcop2moshsq424h6l9rl7uus8kk4dc2". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "aaais4cmjvgu60420jjrs642qdult00s" (unhashed: *.nightquest.dev) with the owner "5ud3ohks9c5ualn3rvdpca7ius0m9n6d" and the NextOwner "apcop2moshsq424h6l9rl7uus8kk4dc2". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 5ud3ohks9c5ualn3rvdpca7ius0m9n6d.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "cdjpoj0olt2gqoooaaoojldaeo1m75s3" equal the hashed NSEC3-owner "cdjpoj0olt2gqoooaaoojldaeo1m75s3" and the hashed NextOwner "p2f4pcof1cd0k96bn3po90ab3scm0r8n". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner cdjpoj0olt2gqoooaaoojldaeo1m75s3.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.



Zone: www.nightquest.dev

www.nightquest.dev
0 DS RR in the parent zone found






RRSIG Type 1 validates the A - Result: 73.159.106.131
Validated: RRSIG-Owner www.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "p2f4pcof1cd0k96bn3po90ab3scm0r8n" equal the hashed NSEC3-owner "p2f4pcof1cd0k96bn3po90ab3scm0r8n" and the hashed NextOwner "19odc4qe7i4odhljqetjt8e66s6vi0u8". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner p2f4pcof1cd0k96bn3po90ab3scm0r8n.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "p2f4pcof1cd0k96bn3po90ab3scm0r8n" equal the hashed NSEC3-owner "p2f4pcof1cd0k96bn3po90ab3scm0r8n" and the hashed NextOwner "19odc4qe7i4odhljqetjt8e66s6vi0u8". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner p2f4pcof1cd0k96bn3po90ab3scm0r8n.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "p2f4pcof1cd0k96bn3po90ab3scm0r8n" equal the hashed NSEC3-owner "p2f4pcof1cd0k96bn3po90ab3scm0r8n" and the hashed NextOwner "19odc4qe7i4odhljqetjt8e66s6vi0u8". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner p2f4pcof1cd0k96bn3po90ab3scm0r8n.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.nightquest.dev) sends a valid NSEC3 RR as result with the hashed owner name "p2f4pcof1cd0k96bn3po90ab3scm0r8n" (unhashed: www.nightquest.dev). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "u3f4dqdi54g2cvrkvr6hne57ihjqvmb5" (unhashed: _tcp.www.nightquest.dev) with the owner "p2f4pcof1cd0k96bn3po90ab3scm0r8n" and the NextOwner "19odc4qe7i4odhljqetjt8e66s6vi0u8". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.www.nightquest.dev) sends a valid NSEC3 RR as result with the owner name "p2f4pcof1cd0k96bn3po90ab3scm0r8n" greater the NextOwner-Name "19odc4qe7i4odhljqetjt8e66s6vi0u8", so the NSEC3 covers the end of the zone. The hashed query name "0kqkq5ms9od14l7co4e4j2jekem6busg" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner p2f4pcof1cd0k96bn3po90ab3scm0r8n.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "7j8obics7cr6tmk4g7ml6p20e8ktra6b" (unhashed: *.www.nightquest.dev) with the owner "5ud3ohks9c5ualn3rvdpca7ius0m9n6d" and the NextOwner "apcop2moshsq424h6l9rl7uus8kk4dc2". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 5ud3ohks9c5ualn3rvdpca7ius0m9n6d.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "p2f4pcof1cd0k96bn3po90ab3scm0r8n" equal the hashed NSEC3-owner "p2f4pcof1cd0k96bn3po90ab3scm0r8n" and the hashed NextOwner "19odc4qe7i4odhljqetjt8e66s6vi0u8". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner p2f4pcof1cd0k96bn3po90ab3scm0r8n.nightquest.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2021, 20:18:14 +, Signature-Inception: 18.06.2021, 20:18:14 +, KeyTag 57379, Signer-Name: nightquest.dev






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.nightquest.dev
•  ns-cloud-e1.googledomains.com
•
nightquest.dev
•  ns-cloud-e1.googledomains.com
216.239.32.110
Montreal/Quebec/Canada (CA) - Google LLC		•

• 
2001:4860:4802:32::6e
Montreal/Quebec/Canada (CA) - Google LLC		•

•  ns-cloud-e2.googledomains.com
216.239.34.110
Montreal/Quebec/Canada (CA) - Google LLC		•

• 
2001:4860:4802:34::6e
Montreal/Quebec/Canada (CA) - Google LLC		•

•  ns-cloud-e3.googledomains.com
216.239.36.110
Montreal/Quebec/Canada (CA) - Google LLC		•

• 
2001:4860:4802:36::6e
Montreal/Quebec/Canada (CA) - Google LLC		•

•  ns-cloud-e4.googledomains.com
216.239.38.110
Montreal/Quebec/Canada (CA) - Google LLC		•

• 
2001:4860:4802:38::6e
Montreal/Quebec/Canada (CA) - Google LLC		•
dev
•  ns-tld1.charlestonroadregistry.com
•

•  ns-tld2.charlestonroadregistry.com
•

•  ns-tld3.charlestonroadregistry.com
•

•  ns-tld4.charlestonroadregistry.com
•

•  ns-tld5.charlestonroadregistry.com
•

 

4. SOA-Entries


Domain:dev
Zone-Name:dev
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


Domain:nightquest.dev
Zone-Name:nightquest.dev
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:15
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.nightquest.dev
Zone-Name:nightquest.dev
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:15
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:1


5. Screenshots

Startaddress: https://nightquest.dev, address used: https://nightquest.dev/, Screenshot created 2021-06-20 20:54:01 +00:0

 

Mobil (412px x 732px)

 

514 milliseconds

 

Screenshot mobile - https://nightquest.dev/
Mobil + Landscape (732px x 412px)

 

529 milliseconds

 

Screenshot mobile landscape - https://nightquest.dev/
Screen (1280px x 1680px)

 

9905 milliseconds

 

Screenshot Desktop - https://nightquest.dev/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412716
content Size560716

 

Fatal: Horizontal scrollbar detected. Content-size width is greater then visual Viewport width.

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_128_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://nightquest.dev/
73.159.106.131
301
https://nightquest.dev/
Html is minified: 108.54 %
0.250
A
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:52:30 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://nightquest.dev/

• http://www.nightquest.dev/
73.159.106.131
301
https://www.nightquest.dev/
Html is minified: 108.54 %
0.250
A
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:52:30 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://www.nightquest.dev/

• https://nightquest.dev/
73.159.106.131 No Compression used - 573 / 675 - 84.89 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/120		200

Html is minified: 125.46 %
Other inline scripts (∑/total): 0/0		3.313
A
small visible content (num chars: 123)
Nightquest, a quest not for the past, but for tomorrow to make it last Simply the best way to walk this life, hand in hand.
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:52:30 GMT
Content-Type: text/html
Content-Length: 675
Last-Modified: Sun, 20 Jun 2021 18:33:10 GMT
Connection: close
ETag: "60cf89e6-2a3"
Strict-Transport-Security: max-age=31536000; includeSubDomains
Accept-Ranges: bytes

• https://www.nightquest.dev/
73.159.106.131
-1


24.120
U
Interner Fehler: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 73.159.106.131:443

• http://nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
73.159.106.131
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.250
A
Visible Content: 301 Moved Permanently nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:52:59 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
73.159.106.131
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://www.nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.250
A
Visible Content: 301 Moved Permanently nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:52:59 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://www.nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 109.46 %
Other inline scripts (∑/total): 0/0		3.654
A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:53:07 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Strict-Transport-Security: max-age=31536000; includeSubDomains

• https://www.nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 109.46 %
Other inline scripts (∑/total): 0/0		12.403
A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:53:11 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Strict-Transport-Security: max-age=31536000; includeSubDomains

• https://73.159.106.131/
73.159.106.131 No Compression used - 573 / 675 - 84.89 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/120		200

Html is minified: 125.46 %
Other inline scripts (∑/total): 0/0		6.640
N
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 123)
Nightquest, a quest not for the past, but for tomorrow to make it last Simply the best way to walk this life, hand in hand.
Server: nginx/1.18.0 (Ubuntu)
Date: Sun, 20 Jun 2021 18:53:00 GMT
Content-Type: text/html
Content-Length: 675
Last-Modified: Sun, 20 Jun 2021 18:33:10 GMT
Connection: close
ETag: "60cf89e6-2a3"
Strict-Transport-Security: max-age=31536000; includeSubDomains
Accept-Ranges: bytes

 

7. Comments


1. General Results, most used to calculate the result

Aname "nightquest.dev" is domain, public suffix is ".dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 12 (complete: 151507)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: nightquest.dev has only one ip address.
Warning: Only one ip address found: www.nightquest.dev has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: nightquest.dev has no ipv6 address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.nightquest.dev has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AExcellent: Domain is in the Google-Preload-List
AExcellent: Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-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)
https://nightquest.dev/ 73.159.106.131


Url with incomplete Content-Type - header - missing charset
https://nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
https://www.nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
https://73.159.106.131/ 73.159.106.131


Url with incomplete Content-Type - header - missing charset
Ahttp://nightquest.dev/ 73.159.106.131
301
https://nightquest.dev/
Correct redirect http - https with the same domain name
Nhttps://73.159.106.131/ 73.159.106.131
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain nightquest.dev, 1 ip addresses, 1 different http results.

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 9 with IPv6, 4 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-e1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-e1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-e1.googledomains.com.
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: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: googledomains.com
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: CA
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 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

AGood: 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.
https://nightquest.dev/ 73.159.106.131
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://73.159.106.131/ 73.159.106.131
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://nightquest.dev/ 73.159.106.131
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://73.159.106.131/ 73.159.106.131
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://nightquest.dev/ 73.159.106.131
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://73.159.106.131/ 73.159.106.131
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
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
https://nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
3.654 seconds
Warning: 404 needs more then one second
https://www.nightquest.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
12.403 seconds
Warning: 404 needs more then one second
ADuration: 203440 milliseconds, 203.440 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
nightquest.dev
73.159.106.131
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
nightquest.dev
73.159.106.131
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=nightquest.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


nightquest.dev
nightquest.dev
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

nightquest.dev
nightquest.dev
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=nightquest.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


www.nightquest.dev
www.nightquest.dev
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

www.nightquest.dev
www.nightquest.dev
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=nightquest.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


73.159.106.131
73.159.106.131
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

73.159.106.131
73.159.106.131
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=nightquest.dev


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US

 

9. Certificates

1.
1.
CN=nightquest.dev
20.06.2021
18.09.2021
1173 days expired		nightquest.dev, www.nightquest.dev - 2 entries
1.
1.
CN=nightquest.dev
20.06.2021

18.09.2021
1173 days expired


nightquest.dev, www.nightquest.dev - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03CD3C6B1F12F33CFECCC429D32AFC70DEEE
Thumbprint:7EDF6C3D754316E51D9B07759AF215CAF8F2B74A
SHA256 / Certificate:Wk0dLMTfPfoqZ0LyK+TgBYzf6bpepzlgiElFVtPiNUs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):752b0d3f1b86c94c79962511c37046e2783e43c1d61c543b0fc0cb92d717c669
SHA256 hex / Subject Public Key Information (SPKI):752b0d3f1b86c94c79962511c37046e2783e43c1d61c543b0fc0cb92d717c669
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 285 days

2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 285 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3834 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3834 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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 - 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

Small Code Update - wait one minute

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

 

QNr.DomainTypeNS used
1
com
NS
f.root-servers.net (2001:500:2f::f)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, 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
2
ns-cloud-e1.googledomains.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
3
ns-cloud-e2.googledomains.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
4
ns-cloud-e3.googledomains.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
5
ns-cloud-e4.googledomains.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
6
ns-cloud-e1.googledomains.com: 216.239.32.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-e1.googledomains.com: 2001:4860:4802:32::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-e2.googledomains.com: 216.239.34.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-e2.googledomains.com: 2001:4860:4802:34::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-e3.googledomains.com: 216.239.36.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-e3.googledomains.com: 2001:4860:4802:36::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-e4.googledomains.com: 216.239.38.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-e4.googledomains.com: 2001:4860:4802:38::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.nightquest.dev
0

no CAA entry found
1
0
nightquest.dev
0

no CAA entry found
1
0
dev
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
nightquest.dev

ok
1
0
www.nightquest.dev

ok
1
0
_acme-challenge.nightquest.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.www.nightquest.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.nightquest.dev.nightquest.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.www.nightquest.dev.nightquest.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.www.nightquest.dev.www.nightquest.dev

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=52eb2c1f-e5ba-4609-b443-63a044c8e0ff

 

Last Result: https://check-your-website.server-daten.de/?q=nightquest.dev - 2021-06-20 20:50:44

 

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

 

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

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions