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




1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
hebbq.tdhttt.org
A

yes
1
0

AAAA
2600:8802:2203:2500:94c5:fe71:b858:48cf
Irvine/California/United States (US) - ASN-CXA-ALL-CCI-22773-RDC

yes


www.hebbq.tdhttt.org

Name Error
yes
1
0
*.tdhttt.org
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.hebbq.tdhttt.org
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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 46594, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 7, KeyTag 17883, DigestType 1 and Digest OMXPk7Npx1V+BRX6qlcGDxv7EsE=



DS with Algorithm 7, KeyTag 17883, DigestType 2 and Digest 2InK15DwGXnoYNZie1j4WrVU4OSR/gZRXzVUjR605u4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.07.2020, 17:00:00 +, Signature-Inception: 04.07.2020, 16:00:00 +, KeyTag 46594, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 27353, Flags 256



Public Key with Algorithm 7, KeyTag 62165, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.07.2020, 15:25:59 +, Signature-Inception: 01.07.2020, 14:25:59 +, KeyTag 17883, Signer-Name: org



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.07.2020, 15:25:59 +, Signature-Inception: 01.07.2020, 14:25:59 +, KeyTag 27353, Signer-Name: org



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 27353 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 17883, DigestType 1 and Digest "OMXPk7Npx1V+BRX6qlcGDxv7EsE=" 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 7, KeyTag 17883, DigestType 2 and Digest "2InK15DwGXnoYNZie1j4WrVU4OSR/gZRXzVUjR605u4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: tdhttt.org
tdhttt.org
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 52900, DigestType 2 and Digest j5OsfHNBPSvcvYdOfavj6ExZBENGSTjX12LnNQ/6lVg=



1 RRSIG RR to validate DS RR found



RRSIG-Owner tdhttt.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.07.2020, 15:25:59 +, Signature-Inception: 01.07.2020, 14:25:59 +, KeyTag 27353, Signer-Name: org



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 43441, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner tdhttt.org., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 52900, Signer-Name: tdhttt.org



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



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

Zone: hebbq.tdhttt.org
hebbq.tdhttt.org
0 DS RR in the parent zone found



0 DNSKEY RR found






RRSIG Type 28 validates the AAAA - Result: 2600:8802:2203:2500:94C5:FE71:B858:48CF
Validated: RRSIG-Owner hebbq.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



A-Query sends a valid NSEC3 RR as result with the hashed query name "sks5bdii16uvhf2uh1n7f3268psatt4i" equal the hashed NSEC3-owner "sks5bdii16uvhf2uh1n7f3268psatt4i" and the hashed NextOwner "4i81qc52poo9mber11dnbsqooed626pi". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner sks5bdii16uvhf2uh1n7f3268psatt4i.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



Status: Good. NoData-Proof required and found.



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "sks5bdii16uvhf2uh1n7f3268psatt4i" equal the hashed NSEC3-owner "sks5bdii16uvhf2uh1n7f3268psatt4i" and the hashed NextOwner "4i81qc52poo9mber11dnbsqooed626pi". 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: AAAA, RRSIG Validated: RRSIG-Owner sks5bdii16uvhf2uh1n7f3268psatt4i.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "sks5bdii16uvhf2uh1n7f3268psatt4i" equal the hashed NSEC3-owner "sks5bdii16uvhf2uh1n7f3268psatt4i" and the hashed NextOwner "4i81qc52poo9mber11dnbsqooed626pi". 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: AAAA, RRSIG Validated: RRSIG-Owner sks5bdii16uvhf2uh1n7f3268psatt4i.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.hebbq.tdhttt.org) sends a valid NSEC3 RR as result with the hashed owner name "sks5bdii16uvhf2uh1n7f3268psatt4i" (unhashed: hebbq.tdhttt.org). So that's the Closest Encloser of the query name.
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner sks5bdii16uvhf2uh1n7f3268psatt4i.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "5td52tavee7ut9neclrduu8r4vnpn7i2" (unhashed: _tcp.hebbq.tdhttt.org) with the owner "4i81qc52poo9mber11dnbsqooed626pi" and the NextOwner "6l0d4dfi4u0prnpirsotspvbdo2258u5". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 4i81qc52poo9mber11dnbsqooed626pi.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



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 "prnjssnsb55he7c2n52b9ciljl5jmi9m" (unhashed: *.hebbq.tdhttt.org) with the owner "6l0d4dfi4u0prnpirsotspvbdo2258u5" and the NextOwner "sks5bdii16uvhf2uh1n7f3268psatt4i". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.hebbq.tdhttt.org) sends a valid NSEC3 RR as result with the hashed query name "f7fnit3ca741n6m6f4j9r27a2agir5e1" between the hashed NSEC3-owner "6l0d4dfi4u0prnpirsotspvbdo2258u5" and the hashed NextOwner "sks5bdii16uvhf2uh1n7f3268psatt4i". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 6l0d4dfi4u0prnpirsotspvbdo2258u5.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "sks5bdii16uvhf2uh1n7f3268psatt4i" equal the hashed NSEC3-owner "sks5bdii16uvhf2uh1n7f3268psatt4i" and the hashed NextOwner "4i81qc52poo9mber11dnbsqooed626pi". 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: AAAA, RRSIG Validated: RRSIG-Owner sks5bdii16uvhf2uh1n7f3268psatt4i.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



Status: Good. NoData-Proof required and found.

Zone: www.hebbq.tdhttt.org
www.hebbq.tdhttt.org
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 "jjgvjs0t1p4ffogdhcp1saqnmmi3of65" between the hashed NSEC3-owner "6l0d4dfi4u0prnpirsotspvbdo2258u5" and the hashed NextOwner "sks5bdii16uvhf2uh1n7f3268psatt4i". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 6l0d4dfi4u0prnpirsotspvbdo2258u5.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "sks5bdii16uvhf2uh1n7f3268psatt4i" as Owner. That's the Hash of "hebbq.tdhttt.org" with the NextHashedOwnerName "4i81qc52poo9mber11dnbsqooed626pi". So that domain name is the Closest Encloser of "www.hebbq.tdhttt.org". Opt-Out: False.
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner sks5bdii16uvhf2uh1n7f3268psatt4i.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org



The ClosestEncloser says, that "*.hebbq.tdhttt.org" with the Hash "prnjssnsb55he7c2n52b9ciljl5jmi9m" 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 "6l0d4dfi4u0prnpirsotspvbdo2258u5" and the Next Owner "sks5bdii16uvhf2uh1n7f3268psatt4i", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 6l0d4dfi4u0prnpirsotspvbdo2258u5.tdhttt.org., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.07.2020, 02:54:40 +, Signature-Inception: 02.07.2020, 02:54:40 +, KeyTag 43441, Signer-Name: tdhttt.org


3. Name Servers

DomainNameserverNS-IP
www.hebbq.tdhttt.org
  ns-cloud-d1.googledomains.com

hebbq.tdhttt.org
  ns-cloud-d1.googledomains.com
216.239.32.109
Sunnyvale/California/United States (US) - Google LLC


 
2001:4860:4802:32::6d
Chicago/Illinois/United States (US) - Google LLC

tdhttt.org
  ns-cloud-d1.googledomains.com
216.239.32.109
Sunnyvale/California/United States (US) - Google LLC


 
2001:4860:4802:32::6d
Chicago/Illinois/United States (US) - Google LLC


  ns-cloud-d2.googledomains.com
216.239.34.109
Sunnyvale/California/United States (US) - Google LLC


 
2001:4860:4802:34::6d
Chicago/Illinois/United States (US) - Google LLC


  ns-cloud-d3.googledomains.com
216.239.36.109
Sunnyvale/California/United States (US) - Google LLC


 
2001:4860:4802:36::6d
Chicago/Illinois/United States (US) - Google LLC


  ns-cloud-d4.googledomains.com
216.239.38.109
Sunnyvale/California/United States (US) - Google LLC


 
2001:4860:4802:38::6d
Chicago/Illinois/United States (US) - Google LLC

org
  a0.org.afilias-nst.info / ns000b.app23.ams2.afilias-nst.info


  a2.org.afilias-nst.info / ns000b.app23.ams2.afilias-nst.info


  b0.org.afilias-nst.org / ns000b.app9.ams2.afilias-nst.info


  b2.org.afilias-nst.org / ns000b.app20.ams2.afilias-nst.info


  c0.org.afilias-nst.info / app3.iad1.hosts.meta.redstone.afilias-nst.info-2


  d0.org.afilias-nst.org / ns000b.app27.ams2.afilias-nst.info


4. SOA-Entries


Domain:org
Zone-Name:org
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013994333
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:tdhttt.org
Zone-Name:tdhttt.org
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:6
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:6


Domain:tdhttt.org
Zone-Name:tdhttt.org
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:7
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:2


Domain:hebbq.tdhttt.org
Zone-Name:tdhttt.org
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:6
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:2


Domain:www.hebbq.tdhttt.org
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
• http://hebbq.tdhttt.org/
2600:8802:2203:2500:94c5:fe71:b858:48cf
-14

10.026
T
Timeout - The operation has timed out

• https://hebbq.tdhttt.org/
2600:8802:2203:2500:94c5:fe71:b858:48cf
-14

10.023
T
Timeout - The operation has timed out

• http://hebbq.tdhttt.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2600:8802:2203:2500:94c5:fe71:b858:48cf
-14

10.027
T
Timeout - The operation has timed out
Visible Content:

• https://[2600:8802:2203:2500:94c5:fe71:b858:48cf]/
2600:8802:2203:2500:94c5:fe71:b858:48cf
-14

10.027
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "hebbq.tdhttt.org" is subdomain, public suffix is ".org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 4510 (complete: 125982)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: hebbq.tdhttt.org has only one ip address.
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.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain hebbq.tdhttt.org, 1 ip addresses.

2. 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, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
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-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-d1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-d1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-d1.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-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.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: US
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: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-cloud-d1.googledomains.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.

3. Content- and Performance-critical Checks

http://hebbq.tdhttt.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:8802:2203:2500:94c5:fe71:b858:48cf
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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
ADuration: 82710 milliseconds, 82.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)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1738647141
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-04 01:06:43
2020-10-02 01:06:43
hebbq.tdhttt.org - 1 entries


1540069061
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-04 05:17:27
2020-07-03 05:17:27
hebbq.tdhttt.org - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
1
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3036981060
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-03 23:06:43
2020-10-01 23:06:43
hebbq.tdhttt.org
1 entries


2665399666
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-04 03:17:27
2020-07-03 03:17:27
hebbq.tdhttt.org
1 entries



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: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

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

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-d1.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2: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-d2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2: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-d3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2: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-d4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2: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-d1.googledomains.com: 216.239.32.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-d1.googledomains.com: 2001:4860:4802:32::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-d2.googledomains.com: 216.239.34.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-d2.googledomains.com: 2001:4860:4802:34::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-d3.googledomains.com: 216.239.36.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-d3.googledomains.com: 2001:4860:4802:36::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-d4.googledomains.com: 216.239.38.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-d4.googledomains.com: 2001:4860:4802:38::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
hebbq.tdhttt.org
0

no CAA entry found
1
0
tdhttt.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tdhttt.org

ok
1
0
hebbq.tdhttt.org

ok
1
0
_acme-challenge.hebbq.tdhttt.org

Name Error - The domain name does not exist
1
0
_acme-challenge.hebbq.tdhttt.org.tdhttt.org

Name Error - The domain name does not exist
1
0
_acme-challenge.hebbq.tdhttt.org.hebbq.tdhttt.org

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=bf035117-6047-459f-8545-988e44b6f4f6


Last Result: https://check-your-website.server-daten.de/?q=hebbq.tdhttt.org - 2020-07-05 03:50:52


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

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