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

0 in Queue, 0 of max. 8 Checks (20:34:27)
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:
14.12.2020 18:06:02

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
maximepzv.dev
A
104.198.14.52
The Dalles/Oregon/United States (US) - Google LLC
Hostname: 52.14.198.104.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.maximepzv.dev

Name Error
yes
1
0
*.maximepzv.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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 26116, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 31.12.2020, 00:00:00 +, Signature-Inception: 10.12.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: 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: 27.12.2020, 05:00:00 +, Signature-Inception: 14.12.2020, 04:00:00 +, KeyTag 26116, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 30846, 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: 03.01.2021, 21:59:06 +, Signature-Inception: 12.12.2020, 21:59: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: maximepzv.dev

maximepzv.dev
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 23680, DigestType 2 and Digest pA5j6OyMI0Om24vcNsthWiUVR9M6fzF4z/6QVES4GMQ=






1 RRSIG RR to validate DS RR found






RRSIG-Owner maximepzv.dev., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 03.01.2021, 21:59:06 +, Signature-Inception: 12.12.2020, 21:59:06 +, KeyTag 30846, Signer-Name: dev






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 22489, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner maximepzv.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 23680, Signer-Name: maximepzv.dev






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






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






RRSIG Type 1 validates the A - Result: 104.198.14.52
Validated: RRSIG-Owner maximepzv.dev., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "losope1nmodltq3fab7cklcmp1s75qs9" equal the hashed NSEC3-owner "losope1nmodltq3fab7cklcmp1s75qs9" and the hashed NextOwner "2u2vepjmjj7rmbmdmo40ff0i64n3940k". 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, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner losope1nmodltq3fab7cklcmp1s75qs9.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "losope1nmodltq3fab7cklcmp1s75qs9" equal the hashed NSEC3-owner "losope1nmodltq3fab7cklcmp1s75qs9" and the hashed NextOwner "2u2vepjmjj7rmbmdmo40ff0i64n3940k". 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, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner losope1nmodltq3fab7cklcmp1s75qs9.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "losope1nmodltq3fab7cklcmp1s75qs9" equal the hashed NSEC3-owner "losope1nmodltq3fab7cklcmp1s75qs9" and the hashed NextOwner "2u2vepjmjj7rmbmdmo40ff0i64n3940k". 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, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner losope1nmodltq3fab7cklcmp1s75qs9.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.maximepzv.dev) sends a valid NSEC3 RR as result with the hashed owner name "losope1nmodltq3fab7cklcmp1s75qs9" (unhashed: maximepzv.dev). So that's the Closest Encloser of the query name. TLSA-Query (_443._tcp.maximepzv.dev) sends a valid NSEC3 RR as result with the owner name "losope1nmodltq3fab7cklcmp1s75qs9" greater the NextOwner-Name "2u2vepjmjj7rmbmdmo40ff0i64n3940k", so the NSEC3 covers the end of the zone. The hashed query name "pi5nbc7rgn0a4v7rdb426u9iegma5uti" comes after the hashed Owner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner losope1nmodltq3fab7cklcmp1s75qs9.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ivbj58d4uc73r1fb19tequ8t2up7mssk" (unhashed: _tcp.maximepzv.dev) with the owner "2u2vepjmjj7rmbmdmo40ff0i64n3940k" and the NextOwner "losope1nmodltq3fab7cklcmp1s75qs9". 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 "avr6e3002uhteifuprmnpoa1vr58dltk" (unhashed: *.maximepzv.dev) with the owner "2u2vepjmjj7rmbmdmo40ff0i64n3940k" and the NextOwner "losope1nmodltq3fab7cklcmp1s75qs9". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 2u2vepjmjj7rmbmdmo40ff0i64n3940k.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "losope1nmodltq3fab7cklcmp1s75qs9" equal the hashed NSEC3-owner "losope1nmodltq3fab7cklcmp1s75qs9" and the hashed NextOwner "2u2vepjmjj7rmbmdmo40ff0i64n3940k". 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, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner losope1nmodltq3fab7cklcmp1s75qs9.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






Status: Good. NoData-Proof required and found.



Zone: www.maximepzv.dev

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






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "losope1nmodltq3fab7cklcmp1s75qs9" as Owner. That's the Hash of "maximepzv.dev" with the NextHashedOwnerName "2u2vepjmjj7rmbmdmo40ff0i64n3940k". So that domain name is the Closest Encloser of "www.maximepzv.dev". Opt-Out: False.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner losope1nmodltq3fab7cklcmp1s75qs9.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev






The ClosestEncloser says, that "*.maximepzv.dev" with the Hash "avr6e3002uhteifuprmnpoa1vr58dltk" 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 "2u2vepjmjj7rmbmdmo40ff0i64n3940k" and the Next Owner "losope1nmodltq3fab7cklcmp1s75qs9", 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 2u2vepjmjj7rmbmdmo40ff0i64n3940k.maximepzv.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.01.2021, 23:51:29 +, Signature-Inception: 10.12.2020, 23:51:29 +, KeyTag 22489, Signer-Name: maximepzv.dev

 

3. Name Servers

DomainNameserverNS-IP
www.maximepzv.dev
•  ns-cloud-d1.googledomains.com

maximepzv.dev
•  ns-cloud-d1.googledomains.com
216.239.32.109
Montreal/Quebec/Canada (CA) - Google LLC		•

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

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

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

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

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

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

• 
2001:4860:4802:38::6d
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:maximepzv.dev
Zone-Name:maximepzv.dev
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:20
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.maximepzv.dev
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://maximepzv.dev, address used: https://maximepzv.dev/, Screenshot created 2020-12-14 18:07:19 +00:0

 

Mobil (412px x 732px)

 

1048 milliseconds

 

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

 

1385 milliseconds

 

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

 

2142 milliseconds

 

Screenshot Desktop - https://maximepzv.dev/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport396732
content Size3962929

 

Good: No horizontal scrollbar. Content-size width = 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_256_GCM.

 

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

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://maximepzv.dev/
104.198.14.52
301
https://maximepzv.dev/
Html is minified: 100.00 %
0.363
A
Cache-Control: public, max-age=0, must-revalidate
Content-Length: 38
Content-Type: text/plain
Date: Mon, 14 Dec 2020 17:06:34 GMT
Location: https://maximepzv.dev/
Age: 0
Connection: close
Server: Netlify
X-NF-Request-ID: 69bb3b17-f1f2-4f0a-8b1c-d43ae89e9e79-35507736

• https://maximepzv.dev/
104.198.14.52
Inline-JavaScript (∑/total): 3/1500 Inline-CSS (∑/total): 0/0		200

Html is minified: 315.79 %
Other inline scripts (∑/total): 1/1500		4.390
A
small visible content (num chars: 46)
You need to enable JavaScript to run this app.
Cache-Control: public, max-age=0, must-revalidate
Content-Type: text/html; charset=UTF-8
Date: Mon, 14 Dec 2020 17:06:35 GMT
Etag: "e5ee2164aa311e9b85217b6aea9b88a4-ssl-df"
Strict-Transport-Security: max-age=31536000
Content-Encoding: gzip
Age: 0
Transfer-Encoding: chunked
Connection: close
Server: Netlify
Vary: Accept-Encoding
X-NF-Request-ID: 69bb3b17-f1f2-4f0a-8b1c-d43ae89e9e79-35508445

• http://maximepzv.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.198.14.52
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://maximepzv.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		0.410
A
Visible Content: Redirecting to https://maximepzv.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Cache-Control: public, max-age=0, must-revalidate
Content-Length: 107
Content-Type: text/plain
Date: Mon, 14 Dec 2020 17:06:40 GMT
Location: https://maximepzv.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Age: 0
Connection: close
Server: Netlify
X-NF-Request-ID: 69bb3b17-f1f2-4f0a-8b1c-d43ae89e9e79-35510955

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

Inline-JavaScript (∑/total): 1/260 Inline-CSS (∑/total): 1/1269		404

Html is minified: 237.65 %
Other inline scripts (∑/total): 1/260		3.817
A
Not Found
Visible Content: Page Not Found Looks like you've followed a broken link or entered a URL that doesn't exist on this site. Back to our site If this is your site, and you weren't expecting a 404 for this path, please visit Netlify's "page not found" support guide for troubleshooting tips.
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
Cache-Control: public, max-age=0, must-revalidate
Content-Type: text/html; charset=utf-8
Date: Mon, 14 Dec 2020 17:06:45 GMT
Etag: 1552516960-ssl-df
Content-Encoding: gzip
Age: 0
Transfer-Encoding: chunked
Connection: close
Server: Netlify
Vary: Accept-Encoding
X-NF-Request-ID: 69bb3b17-f1f2-4f0a-8b1c-d43ae89e9e79-35514086

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

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		4.014
N
Not Found
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 69)
Not found - Request ID: 69bb3b17-f1f2-4f0a-8b1c-d43ae89e9e79-35511338
Cache-Control: private, max-age=0
Content-Length: 69
Content-Type: text/plain; charset=utf-8
Date: Mon, 14 Dec 2020 17:06:40 GMT
Age: 0
Connection: close
Server: Netlify
X-NF-Request-ID: 69bb3b17-f1f2-4f0a-8b1c-d43ae89e9e79-35511338

 

7. Comments


1. General Results, most used to calculate the result

Aname "maximepzv.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: 131120)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: maximepzv.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: maximepzv.dev has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://maximepzv.dev/ 104.198.14.52
301
https://maximepzv.dev/
Correct redirect http - https with the same domain name
Bhttps://maximepzv.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404

Missing HSTS-Header
Mhttps://104.198.14.52/ 104.198.14.52
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://104.198.14.52/ 104.198.14.52
404

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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain maximepzv.dev, 1 ip addresses.

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, 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: 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
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.

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.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://maximepzv.dev/ 104.198.14.52
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://maximepzv.dev/ 104.198.14.52
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.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
https://maximepzv.dev/ 104.198.14.52
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 4 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 4 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 4 complete.
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://maximepzv.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
3.817 seconds
Warning: 404 needs more then one second
https://104.198.14.52/ 104.198.14.52
404
4.014 seconds
Warning: 404 needs more then one second
ADuration: 82874 milliseconds, 82.874 seconds

 

8. Connections

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

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
SNI required 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=maximepzv.dev


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


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

maximepzv.dev
maximepzv.dev
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=maximepzv.dev


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


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

104.198.14.52
104.198.14.52
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=*.netlify.com, O="Netlify, Inc", L=San Francisco, C=US, ST=ca


2CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US

 

9. Certificates

1.
1.
CN=maximepzv.dev
10.12.2020
10.03.2021
1365 days expired		maximepzv.dev - 1 entry
1.
1.
CN=maximepzv.dev
10.12.2020

10.03.2021
1365 days expired


maximepzv.dev - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03B001DE7ABC299826A781ECB739857BB5F3
Thumbprint:C25EEFEC59D953896CD46F75B36EF70DE6CFD38E
SHA256 / Certificate:4wzQuu/r+YPJfu6nOKU/tySfa4FbOjJxM+grMu+Sz64=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):5f1b2badf92a9e3c87d89c259bfbf02a0b12f2a705a2e27c1f9d6b54d6db48a4
SHA256 hex / Subject Public Key Information (SPKI):5f1b2badf92a9e3c87d89c259bfbf02a0b12f2a705a2e27c1f9d6b54d6db48a4
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
07.10.2020
29.09.2021
1162 days expired

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

29.09.2021
1162 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:400175048314A4C8218C84A90C16CDDF
Thumbprint:48504E974C0DAC5B5CD476C8202274B24C8C7172
SHA256 / Certificate:cwwb3NhfV85dwLunM+XxulqSWyp3HWQKJvekVCJNrTs=
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1161 days expired

3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1161 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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:




2.
1.
CN=*.netlify.com, O="Netlify, Inc", L=San Francisco, S=ca, C=US
15.06.2020
03.08.2021
1219 days expired		*.netlify.com, netlify.com - 2 entries
2.
1.
CN=*.netlify.com, O="Netlify, Inc", L=San Francisco, S=ca, C=US
15.06.2020

03.08.2021
1219 days expired


*.netlify.com, netlify.com - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0B2A4CDA862F17E1649320A3F5B1B0E3
Thumbprint:C10FB1FBF1ED579B12291697B849B868072B9C65
SHA256 / Certificate:j/2gRgE/CS245lNQeuRNFTpnbb/dND8F9E0UqOzFhqQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):128d720b883cee7d62a5889983fa44ab50217bfe09aad7272b089a1260cff7cc
SHA256 hex / Subject Public Key Information (SPKI):128d720b883cee7d62a5889983fa44ab50217bfe09aad7272b089a1260cff7cc
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
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=*.netlify.com, O="Netlify, Inc", L=San Francisco, S=ca, C=US
15.06.2020
03.08.2021
1219 days expired		*.netlify.com, netlify.com - 2 entries

2.
CN=*.netlify.com, O="Netlify, Inc", L=San Francisco, S=ca, C=US
15.06.2020

03.08.2021
1219 days expired


*.netlify.com, netlify.com - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0B2A4CDA862F17E1649320A3F5B1B0E3
Thumbprint:C10FB1FBF1ED579B12291697B849B868072B9C65
SHA256 / Certificate:j/2gRgE/CS245lNQeuRNFTpnbb/dND8F9E0UqOzFhqQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):128d720b883cee7d62a5889983fa44ab50217bfe09aad7272b089a1260cff7cc
SHA256 hex / Subject Public Key Information (SPKI):128d720b883cee7d62a5889983fa44ab50217bfe09aad7272b089a1260cff7cc
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
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)




3.
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
08.03.2013
08.03.2023
637 days expired

3.
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
08.03.2013

08.03.2023
637 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:01FDA3EB6ECA75C888438B724BCFBC91
Thumbprint:1FB86B1168EC743154062E8C9CC5B171A4B7CCB4
SHA256 / Certificate:FUxDPEkZKcXvaG6DjjI2ZKAOag2CLMyVj7TasD5JoI8=
SHA256 hex / Cert (DANE * 0 1):154c433c491929c5ef686e838e323664a00e6a0d822ccc958fb4dab03e49a08f
SHA256 hex / PublicKey (DANE * 1 1):e6426f344330d0a8eb080bbb7976391d976fc824b5dc16c0d15246d5148ff75c
SHA256 hex / Subject Public Key Information (SPKI):e6426f344330d0a8eb080bbb7976391d976fc824b5dc16c0d15246d5148ff75c
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




4.
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
08.03.2013
08.03.2023
637 days expired

4.
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
08.03.2013

08.03.2023
637 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:01FDA3EB6ECA75C888438B724BCFBC91
Thumbprint:1FB86B1168EC743154062E8C9CC5B171A4B7CCB4
SHA256 / Certificate:FUxDPEkZKcXvaG6DjjI2ZKAOag2CLMyVj7TasD5JoI8=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):e6426f344330d0a8eb080bbb7976391d976fc824b5dc16c0d15246d5148ff75c
SHA256 hex / Subject Public Key Information (SPKI):e6426f344330d0a8eb080bbb7976391d976fc824b5dc16c0d15246d5148ff75c
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




5.
CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006
10.11.2031
expires in 2532 days

5.
CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006

10.11.2031
expires in 2532 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:083BE056904246B1A1756AC95991C74A
Thumbprint:A8985D3A65E5E5C4B2D7D66D40C6DD2FB19C5436
SHA256 / Certificate:Q0ig6URMeMsmXgWNXolEtNhPlmK9Jtslf4k0pEPHAWE=
SHA256 hex / Cert (DANE * 0 1):4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
SHA256 hex / PublicKey (DANE * 1 1):aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391
SHA256 hex / Subject Public Key Information (SPKI):aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391
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:





6.
CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
07.12.2016
10.05.2025
expires in 157 days

6.
CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
07.12.2016

10.05.2025
expires in 157 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0F5BC3A176CB789E2020C7893C8167B4
Thumbprint:FB20FA8A6A93B375F054814F9E00273EA51A6138
SHA256 / Certificate:bay7iUUTex2tQhGwQ2774G8SrONpBJc7Ra4ldAgj02k=
SHA256 hex / Cert (DANE * 0 1):6dacbb8945137b1dad4211b0436efbe06f12ace36904973b45ae25740823d369
SHA256 hex / PublicKey (DANE * 1 1):aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391
SHA256 hex / Subject Public Key Information (SPKI):aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




7.
CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE
12.05.2000
13.05.2025
expires in 160 days

7.
CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE
12.05.2000

13.05.2025
expires in 160 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:020000B9
Thumbprint:D4DE20D05E66FC53FE1A50882C78DB2852CAE474
SHA256 / Certificate:Fq9XqfZ2sKsSYJWqXrre8iqzERnWRKyVzUuT2/Pyaus=
SHA256 hex / Cert (DANE * 0 1):16af57a9f676b0ab126095aa5ebadef22ab31119d644ac95cd4b93dbf3f26aeb
SHA256 hex / PublicKey (DANE * 1 1):63d9af9b47b1064d49a10e7b7fd566dbc8caa399459bfc2829c571ad8c6ef34a
SHA256 hex / Subject Public Key Information (SPKI):63d9af9b47b1064d49a10e7b7fd566dbc8caa399459bfc2829c571ad8c6ef34a
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)

Small Code Update - wait one minute

 

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

 

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

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)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
maximepzv.dev
0

no CAA entry found
1
0
dev
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
maximepzv.dev

ok
1
0
_acme-challenge.maximepzv.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.maximepzv.dev.maximepzv.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=16f08f4f-1fdc-4033-8d88-1e7ea1a1b166

 

Last Result: https://check-your-website.server-daten.de/?q=maximepzv.dev - 2020-12-14 18:06:02

 

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

 

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