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


 

 

U

 

No dns entry found - perhaps mistype. Or wrong IDN

 

Checked:
03.04.2024 01:47:12

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
crystal.degruiter.waytohey.com

Name Error
yes
1
0
www.crystal.degruiter.waytohey.com

Name Error
yes
1
0
*.degruiter.waytohey.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.crystal.degruiter.waytohey.com
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 5613, Flags 256






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






Public Key with Algorithm 8, KeyTag 30903, 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.2024, 00:00:00 +, Signature-Inception: 01.04.2024, 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






DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2024, 18:00:00 +, Signature-Inception: 02.04.2024, 17:00:00 +, KeyTag 5613, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 4534, Flags 256






Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.04.2024, 14:02:35 +, Signature-Inception: 28.03.2024, 13:57:35 +, KeyTag 19718, Signer-Name: com






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






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



Zone: waytohey.com

waytohey.com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 48484, DigestType 2 and Digest 0ef3HNw3/ohcqjNvCWq3OR531Rlxz5Y8T5gBlwlH6eI=






1 RRSIG RR to validate DS RR found






RRSIG-Owner waytohey.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 07.04.2024, 04:18:38 +, Signature-Inception: 31.03.2024, 03:08:38 +, KeyTag 4534, Signer-Name: com






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 55908, Flags 256






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner waytohey.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 48484, Signer-Name: waytohey.com






RRSIG-Owner waytohey.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com






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






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






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



Zone: degruiter.waytohey.com

degruiter.waytohey.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 "om8kpp0klffi3vih649h6v5m6shq1o9c" between the hashed NSEC3-owner "oeta6f2mjc5g95jogq6ptgqm393b2ek0" and the hashed NextOwner "p4f7s0eqt1it0qim28gavl1jo8305bsi". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner oeta6f2mjc5g95jogq6ptgqm393b2ek0.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "95f91iaa9cfccorepgjf431r6pun474e" as Owner. That's the Hash of "waytohey.com" with the NextHashedOwnerName "9ga23brpkkgnh84urnevtb5s15u0c0e0". So that domain name is the Closest Encloser of "degruiter.waytohey.com". Opt-Out: True.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 95f91iaa9cfccorepgjf431r6pun474e.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com






The ClosestEncloser says, that "*.waytohey.com" with the Hash "4ugtem9ms3oq2k9k59bbeh84j0f2husr" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "4fpvs2q7crhigatr2nibcbb2snpio4ta" and the Next Owner "5rjvqcajdq0055npv59sed66aj9up5g3", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 4fpvs2q7crhigatr2nibcbb2snpio4ta.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com



Zone: crystal.degruiter.waytohey.com

crystal.degruiter.waytohey.com
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "95f91iaa9cfccorepgjf431r6pun474e" as Owner. That's the Hash of "waytohey.com" with the NextHashedOwnerName "9ga23brpkkgnh84urnevtb5s15u0c0e0". So that domain name is the Closest Encloser of "crystal.degruiter.waytohey.com". Opt-Out: True.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 95f91iaa9cfccorepgjf431r6pun474e.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com






The ClosestEncloser says, that "*.waytohey.com" with the Hash "4ugtem9ms3oq2k9k59bbeh84j0f2husr" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "4fpvs2q7crhigatr2nibcbb2snpio4ta" and the Next Owner "5rjvqcajdq0055npv59sed66aj9up5g3", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 4fpvs2q7crhigatr2nibcbb2snpio4ta.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com



Zone: www.crystal.degruiter.waytohey.com

www.crystal.degruiter.waytohey.com
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "95f91iaa9cfccorepgjf431r6pun474e" as Owner. That's the Hash of "waytohey.com" with the NextHashedOwnerName "9ga23brpkkgnh84urnevtb5s15u0c0e0". So that domain name is the Closest Encloser of "www.crystal.degruiter.waytohey.com". Opt-Out: True.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 95f91iaa9cfccorepgjf431r6pun474e.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com






The ClosestEncloser says, that "*.waytohey.com" with the Hash "4ugtem9ms3oq2k9k59bbeh84j0f2husr" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "4fpvs2q7crhigatr2nibcbb2snpio4ta" and the Next Owner "5rjvqcajdq0055npv59sed66aj9up5g3", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 4fpvs2q7crhigatr2nibcbb2snpio4ta.waytohey.com., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 03.05.2024, 03:40:01 +, Signature-Inception: 01.04.2024, 03:40:01 +, KeyTag 55908, Signer-Name: waytohey.com

 

3. Name Servers

DomainNameserverNS-IP
www.crystal.degruiter.waytohey.com
  ns1.waytohey.com

crystal.degruiter.waytohey.com
  ns1.waytohey.com

degruiter.waytohey.com
  ns1.waytohey.com

waytohey.com
  ns1.waytohey.com
91.240.86.68
St Petersburg/St.-Petersburg/Russia (RU) - JSC IOT


 
2a01:230:2:41::20c
Moscow/Russia (RU) - JSC IOT


  ns2.waytohey.com
188.34.179.104
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH


 
2a01:4f8:1c17:4f76::5
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH

com
  a.gtld-servers.net / nnn1-defra-5


  b.gtld-servers.net / nnn1-eltxl1


  c.gtld-servers.net / nnn1-defra-5


  d.gtld-servers.net / nnn1-defra-5


  e.gtld-servers.net / nnn1-defra-5


  f.gtld-servers.net / nnn1-defra-4


  g.gtld-servers.net / nnn1-defra-4


  h.gtld-servers.net / nnn1-defra-4


  i.gtld-servers.net / nnn1-defra-4


  j.gtld-servers.net / nnn1-ein3


  k.gtld-servers.net / nnn1-ein4


  l.gtld-servers.net / nnn1-ein4


  m.gtld-servers.net / nnn1-nlams-2e

 

4. SOA-Entries


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


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


Domain:waytohey.com
Zone-Name:waytohey.com
Primary:ns1.waytohey.com
Mail:ns2.waytohey.com
Serial:2024040102
Refresh:60
Retry:60
Expire:86000
TTL:60
num Entries:4


Domain:degruiter.waytohey.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:crystal.degruiter.waytohey.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.crystal.degruiter.waytohey.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








 

7. Comments


1. General Results, most used to calculate the result

Aname "crystal.degruiter.waytohey.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 93017 (complete: 240622)
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.crystal.degruiter.waytohey.com

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

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.waytohey.com (2a01:230:2:41::20c, 91.240.86.68), ns2.waytohey.com (188.34.179.104, 2a01:4f8:1c17:4f76::5)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.waytohey.com, ns2.waytohey.com, 2 Name Servers included in Delegation: ns1.waytohey.com, ns2.waytohey.com, 2 Name Servers included in 1 Zone definitions: ns1.waytohey.com, ns2.waytohey.com, 1 Name Servers listed in SOA.Primary: ns1.waytohey.com.
AGood: Only one SOA.Primary Name Server found.: ns1.waytohey.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.waytohey.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.
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 188., 91., 2 different subnets (first two Bytes): 188.34., 91.240., 2 different subnets (first three Bytes): 188.34.179., 91.240.86.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a01:, 2 different subnets (first two blocks): 2a01:0230:, 2a01:04f8:, 2 different subnets (first three blocks): 2a01:0230:0002:, 2a01:04f8:1c17:, 2 different subnets (first four blocks): 2a01:0230:0002:0041:, 2a01:04f8:1c17:4f76:
AGood: Name Server IPv6 addresses from different subnets found.
Nameserver doesn't pass all EDNS-Checks: ns1.waytohey.com: 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: ns1.waytohey.com: 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: ns1.waytohey.com: 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.

4. Content- and Performance-critical Checks

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. 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: 41993 milliseconds, 41.993 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.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.

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.waytohey.com, ns2.waytohey.com

 

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

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
ns1.waytohey.com: 2a01:230:2:41::20c, 91.240.86.68
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.waytohey.com
188.34.179.104, 2a01:4f8:1c17:4f76::5

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
waytohey.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

No TXT entries found

 

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=1c7e87bc-fa37-4945-8dde-5b4e074b0e39

 

Last Result: https://check-your-website.server-daten.de/?q=crystal.degruiter.waytohey.com - 2024-04-03 01:47:12

 

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

 

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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=crystal.degruiter.waytohey.com