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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
18.03.2023 21:06:52

Older results

X - 18.03.2023 21:04:44

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
meinhold.app	A		yes	1	0
	AAAA		yes
www.meinhold.app		Name Error	yes	1	0
*.meinhold.app	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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 951, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 23684, DigestType 2 and Digest OlzIox4CyUq6ZGGRL6u36fXjSVe7YRSlWoZNlq7DGDY=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.03.2023, 17:00:00 +, Signature-Inception: 18.03.2023, 16:00:00 +, KeyTag 951, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 27853, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 06.04.2023, 18:54:22 +, Signature-Inception: 15.03.2023, 18:54:22 +, KeyTag 23684, Signer-Name: app


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


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

Zone: meinhold.app
meinhold.app	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 62737, DigestType 2 and Digest VU/Mdks6Shtf45j+BfI9StmgB1XMp9NUNxEbmnZHklA=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner meinhold.app., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 06.04.2023, 18:54:22 +, Signature-Inception: 15.03.2023, 18:54:22 +, KeyTag 27853, Signer-Name: app


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 22725, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner meinhold.app., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 62737, Signer-Name: meinhold.app


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


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


	A-Query sends a valid NSEC3 RR as result with the hashed query name "pj7csuht2nqgplbiqobh318i8q4ehvpv" equal the hashed NSEC3-owner "pj7csuht2nqgplbiqobh318i8q4ehvpv" and the hashed NextOwner "dkoikl9vetnhvuq3psfcdifd126co0aq". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "pj7csuht2nqgplbiqobh318i8q4ehvpv" equal the hashed NSEC3-owner "pj7csuht2nqgplbiqobh318i8q4ehvpv" and the hashed NextOwner "dkoikl9vetnhvuq3psfcdifd126co0aq". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "pj7csuht2nqgplbiqobh318i8q4ehvpv" equal the hashed NSEC3-owner "pj7csuht2nqgplbiqobh318i8q4ehvpv" and the hashed NextOwner "dkoikl9vetnhvuq3psfcdifd126co0aq". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "pj7csuht2nqgplbiqobh318i8q4ehvpv" equal the hashed NSEC3-owner "pj7csuht2nqgplbiqobh318i8q4ehvpv" and the hashed NextOwner "dkoikl9vetnhvuq3psfcdifd126co0aq". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.meinhold.app) sends a valid NSEC3 RR as result with the hashed owner name "pj7csuht2nqgplbiqobh318i8q4ehvpv" (unhashed: meinhold.app). 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 "6eblivjf6dq904fmv8dgscntqjhdp9g9" (unhashed: _tcp.meinhold.app) with the owner "pj7csuht2nqgplbiqobh318i8q4ehvpv" and the NextOwner "dkoikl9vetnhvuq3psfcdifd126co0aq". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.meinhold.app) sends a valid NSEC3 RR as result with the owner name "pj7csuht2nqgplbiqobh318i8q4ehvpv" greater the NextOwner-Name "dkoikl9vetnhvuq3psfcdifd126co0aq", so the NSEC3 covers the end of the zone. The hashed query name "qb0p558j00brh9uc70dt508sa7tokl7r" comes after the hashed Owner, so the zone confirmes the not-existence of that TLSA RR. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	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 "g4onmj7l01b1vhecq6ejbtu9ao5rj453" (unhashed: *.meinhold.app) with the owner "dkoikl9vetnhvuq3psfcdifd126co0aq" and the NextOwner "pj7csuht2nqgplbiqobh318i8q4ehvpv". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner dkoikl9vetnhvuq3psfcdifd126co0aq.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "pj7csuht2nqgplbiqobh318i8q4ehvpv" equal the hashed NSEC3-owner "pj7csuht2nqgplbiqobh318i8q4ehvpv" and the hashed NextOwner "dkoikl9vetnhvuq3psfcdifd126co0aq". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	Status: Good. NoData-Proof required and found.

Zone: www.meinhold.app
www.meinhold.app	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 "mshmaqvkmlo3q5rtrnb01dt0o3g9896h" between the hashed NSEC3-owner "dkoikl9vetnhvuq3psfcdifd126co0aq" and the hashed NextOwner "pj7csuht2nqgplbiqobh318i8q4ehvpv". So the parent zone confirmes the not-existence of a DS RR. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner dkoikl9vetnhvuq3psfcdifd126co0aq.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "pj7csuht2nqgplbiqobh318i8q4ehvpv" as Owner. That's the Hash of "meinhold.app" with the NextHashedOwnerName "dkoikl9vetnhvuq3psfcdifd126co0aq". So that domain name is the Closest Encloser of "www.meinhold.app". Opt-Out: False. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner pj7csuht2nqgplbiqobh318i8q4ehvpv.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app


	The ClosestEncloser says, that "*.meinhold.app" with the Hash "g4onmj7l01b1vhecq6ejbtu9ao5rj453" 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 "dkoikl9vetnhvuq3psfcdifd126co0aq" and the Next Owner "pj7csuht2nqgplbiqobh318i8q4ehvpv", 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 dkoikl9vetnhvuq3psfcdifd126co0aq.meinhold.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 08.04.2023, 10:37:30 +, Signature-Inception: 17.03.2023, 10:37:30 +, KeyTag 22725, Signer-Name: meinhold.app

3. Name Servers

Domain	Nameserver	NS-IP
www.meinhold.app	• ns-cloud-c1.googledomains.com
meinhold.app	• ns-cloud-c1.googledomains.com	216.239.32.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6c Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-c2.googledomains.com	216.239.34.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:34::6c Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-c3.googledomains.com	216.239.36.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:36::6c Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-c4.googledomains.com	216.239.38.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:38::6c Montreal/Quebec/Canada (CA) - Google LLC	•
app	• ns-tld1.charlestonroadregistry.com		•
	• ns-tld2.charlestonroadregistry.com		•
	• ns-tld3.charlestonroadregistry.com		•
	• ns-tld4.charlestonroadregistry.com		•
	• ns-tld5.charlestonroadregistry.com		•

4. SOA-Entries

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

Domain:	meinhold.app
Zone-Name:	meinhold.app
Primary:	ns-cloud-c1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	2
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	8

Domain:	www.meinhold.app
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "meinhold.app" is domain, public suffix is ".app", top-level-domain is ".app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .app-domains preloaded: 44 (complete: 220007)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Excellent: Domain is in the Google-Preload-List
A	Excellent: Domain is in the Mozilla/Firefox-Preload-List
A	HSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
B	No _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.meinhold.app
	2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
A	Good: 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.
A	Info:: 4 different Name Servers found: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-c1.googledomains.com.
A	Good: Only one SOA.Primary Name Server found.: ns-cloud-c1.googledomains.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns-cloud-c1.googledomains.com.
A	Good: 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-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
A	Good: 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
A	Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
A	Info: 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.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: 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:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 8 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 8 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns-cloud-c1.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.
A	Good: 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
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 39890 milliseconds, 39.890 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: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

QNr.	Domain	Type	NS used
1	com	NS	b.root-servers.net (2001:500:200::b)
	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-c1.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-c2.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-c3.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-c4.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-c1.googledomains.com: 216.239.32.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
7	ns-cloud-c1.googledomains.com: 2001:4860:4802:32::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
8	ns-cloud-c2.googledomains.com: 216.239.34.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
9	ns-cloud-c2.googledomains.com: 2001:4860:4802:34::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
10	ns-cloud-c3.googledomains.com: 216.239.36.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
11	ns-cloud-c3.googledomains.com: 2001:4860:4802:36::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
12	ns-cloud-c4.googledomains.com: 216.239.38.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
13	ns-cloud-c4.googledomains.com: 2001:4860:4802:38::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)

13. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
meinhold.app	0		no CAA entry found	1	0
app	0		no CAA entry found	1	0

14. TXT - Entries

Domainname	Status	∑ Queries
meinhold.app	ok	1
_acme-challenge.meinhold.app	Name Error - The domain name does not exist	1
_acme-challenge.meinhold.app.meinhold.app	Name Error - The domain name does not exist	1

15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

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=cdcf7c44-8a34-4f0a-bfd8-c4ed8ea3fd56

Last Result: https://check-your-website.server-daten.de/?q=meinhold.app - 2023-03-18 21:06: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=meinhold.app" target="_blank">Check this Site: meinhold.app</a>

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