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




U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
30.04.2023 08:13:50


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
weisse-schaeferhunde.dog

Name Error
yes
1
0
www.weisse-schaeferhunde.dog

Name Error
yes
1
0


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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 60955, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 48736, DigestType 2 and Digest Su3z07XRHDPFo5utvhcI06/GJ2WCvx7oDnOmZ+u1Q8A=



1 RRSIG RR to validate DS RR found



RRSIG-Owner dog., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 13.05.2023, 05:00:00 +, Signature-Inception: 30.04.2023, 04:00:00 +, KeyTag 60955, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 9450, Flags 256



Public Key with Algorithm 8, KeyTag 15561, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner dog., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 16.05.2023, 15:36:00 +, Signature-Inception: 25.04.2023, 14:36:00 +, KeyTag 48736, Signer-Name: dog



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



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

Zone: weisse-schaeferhunde.dog
weisse-schaeferhunde.dog
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 "38nc0upoad4lf3pldjct5fbm2e5gfkdd" between the hashed NSEC3-owner "371hn11vnqeerkn5f0dv766kqihng1lt" and the hashed NextOwner "39ejuc5ij704f08tq8u7dupugi4t6l15". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 371hn11vnqeerkn5f0dv766kqihng1lt.dog., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.05.2023, 15:36:00 +, Signature-Inception: 25.04.2023, 14:36:00 +, KeyTag 15561, Signer-Name: dog



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "hdsv4g7ft7nf445n3g0e7mc2bl1037q2" as Owner. That's the Hash of "dog" with the NextHashedOwnerName "he5kl73dn1dakd80ojjs89a558k0sr31". So that domain name is the Closest Encloser of "weisse-schaeferhunde.dog". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner hdsv4g7ft7nf445n3g0e7mc2bl1037q2.dog., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 21.05.2023, 06:03:14 +, Signature-Inception: 30.04.2023, 05:03:14 +, KeyTag 15561, Signer-Name: dog



The ClosestEncloser says, that "*.dog" with the Hash "m13ruu5r9js5sh5fv9gse31rd6bucuf1" 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 "m0grvn7n9n35r9i3bpd7n6av3hsi2a3b" and the Next Owner "m1j193i3u4h688cfjv195e9h2pqt1j3i", 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: NS, DS, RRSIG Validated: RRSIG-Owner m0grvn7n9n35r9i3bpd7n6av3hsi2a3b.dog., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.05.2023, 15:36:00 +, Signature-Inception: 25.04.2023, 14:36:00 +, KeyTag 15561, Signer-Name: dog

Zone: www.weisse-schaeferhunde.dog
www.weisse-schaeferhunde.dog
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "hdsv4g7ft7nf445n3g0e7mc2bl1037q2" as Owner. That's the Hash of "dog" with the NextHashedOwnerName "he5kl73dn1dakd80ojjs89a558k0sr31". So that domain name is the Closest Encloser of "www.weisse-schaeferhunde.dog". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner hdsv4g7ft7nf445n3g0e7mc2bl1037q2.dog., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 21.05.2023, 06:03:14 +, Signature-Inception: 30.04.2023, 05:03:14 +, KeyTag 15561, Signer-Name: dog



The ClosestEncloser says, that "*.dog" with the Hash "m13ruu5r9js5sh5fv9gse31rd6bucuf1" 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 "m0grvn7n9n35r9i3bpd7n6av3hsi2a3b" and the Next Owner "m1j193i3u4h688cfjv195e9h2pqt1j3i", 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: NS, DS, RRSIG Validated: RRSIG-Owner m0grvn7n9n35r9i3bpd7n6av3hsi2a3b.dog., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.05.2023, 15:36:00 +, Signature-Inception: 25.04.2023, 14:36:00 +, KeyTag 15561, Signer-Name: dog


3. Name Servers

DomainNameserverNS-IP
www.weisse-schaeferhunde.dog
  v0n0.nic.dog

weisse-schaeferhunde.dog
  v0n0.nic.dog

dog
  v0n0.nic.dog / app9.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  v0n1.nic.dog / app26.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  v0n2.nic.dog / app17.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  v0n3.nic.dog / app14.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  v2n0.nic.dog / FRA5


  v2n1.nic.dog / FRA6


4. SOA-Entries


Domain:dog
Zone-Name:dog
Primary:v0n0.nic.dog
Mail:hostmaster.donuts.email
Serial:1682834338
Refresh:7200
Retry:900
Expire:1209600
TTL:3600
num Entries:6


Domain:weisse-schaeferhunde.dog
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.weisse-schaeferhunde.dog
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 "weisse-schaeferhunde.dog" is domain, public suffix is ".dog", top-level-domain is ".dog", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .dog-domains preloaded: 31 (complete: 221801)
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.weisse-schaeferhunde.dog

2. Header-Checks

U

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

3. DNS- and NameServer - Checks

A
A
AInfo:: 6 different Name Servers found: v0n0.nic.dog, v0n1.nic.dog, v0n2.nic.dog, v0n3.nic.dog, v2n0.nic.dog, v2n1.nic.dog, 6 Name Servers included in Delegation: v0n0.nic.dog, v0n1.nic.dog, v0n2.nic.dog, v0n3.nic.dog, v2n0.nic.dog, v2n1.nic.dog, 6 Name Servers included in 1 Zone definitions: v0n0.nic.dog, v0n1.nic.dog, v0n2.nic.dog, v0n3.nic.dog, v2n0.nic.dog, v2n1.nic.dog, 1 Name Servers listed in SOA.Primary: v0n0.nic.dog.
AGood: Only one SOA.Primary Name Server found.: v0n0.nic.dog.
AGood: SOA.Primary Name Server included in the delegation set.: v0n0.nic.dog.
AGood: All Name Server Domain Names have a Public Suffix.
A
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: v0n0.nic.dog: 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: v0n0.nic.dog: 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: 37960 milliseconds, 37.960 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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
dog
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=04f9fb49-fbfb-49d7-8f30-ebb0dc54d946


Last Result: https://check-your-website.server-daten.de/?q=weisse-schaeferhunde.dog - 2023-04-30 08:13:50


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

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

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