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

...

skip EDNS-Check

skip Content-Check

check links

Tls-Protocol error

Checked:
29.11.2024 11:27:02

Older results

V - 29.11.2024 11:01:43

V - 29.11.2024 10:53:29

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
pastagacorporation.fr	A	51.83.72.179 Tourcoing/Hauts-de-France/France (FR) - OVH SAS Hostname: vps-6efce74c.vps.ovh.net	yes	1	0
	AAAA	2001:41d0:304:200::6673 Gravelines/Hauts-de-France/France (FR) - OVH SAS	yes
www.pastagacorporation.fr		Name Error	yes	1	0
*.pastagacorporation.fr	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 61050, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2024, 00:00:00 +, Signature-Inception: 20.11.2024, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


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

Zone: fr
fr	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 29133, DigestType 2 and Digest EwPo2o+2DbUA1b6h7l3JorzJPf4vxD00ZXZlj+zPV0k=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2024, 05:00:00 +, Signature-Inception: 29.11.2024, 04:00:00 +, KeyTag 61050, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 44829, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner fr., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 30.12.2024, 17:51:29 +, Signature-Inception: 31.10.2024, 16:55:37 +, KeyTag 29133, Signer-Name: fr


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


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

Zone: pastagacorporation.fr
pastagacorporation.fr	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 27775, DigestType 2 and Digest HM3JpTk0RDdZkACvMPuLjE7KtwgBHQId6MtnBicNfDU=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner pastagacorporation.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 31.12.2024, 13:31:32 +, Signature-Inception: 25.11.2024, 16:41:54 +, KeyTag 44829, Signer-Name: fr


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 6813, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner pastagacorporation.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	RRSIG-Owner pastagacorporation.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 27775, Signer-Name: pastagacorporation.fr


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


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


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


	RRSIG Type 1 validates the A - Result: 51.83.72.179 Validated: RRSIG-Owner pastagacorporation.fr., Algorithm: 8, 2 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	RRSIG Type 16 validates the TXT - Result: v=spf1 a include:mx.ovh.com ~all Validated: RRSIG-Owner pastagacorporation.fr., Algorithm: 8, 2 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	RRSIG Type 28 validates the AAAA - Result: 2001:41D0:0304:0200:0000:0000:0000:6673 Validated: RRSIG-Owner pastagacorporation.fr., Algorithm: 8, 2 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "6l96oh78qa1mdqkji23do90t9iid48fv" equal the hashed NSEC3-owner "6l96oh78qa1mdqkji23do90t9iid48fv" and the hashed NextOwner "8tqofg89d3qvdmbriiu2c2fr1ikqn0lp". 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, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 6l96oh78qa1mdqkji23do90t9iid48fv.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.pastagacorporation.fr) sends a valid NSEC3 RR as result with the hashed owner name "vpf9f4eq1j17mlacpidfj5q4v6n4fm93" (unhashed: _tcp.pastagacorporation.fr). So that's the Closest Encloser of the query name. Bitmap: No Bitmap? Validated: RRSIG-Owner vpf9f4eq1j17mlacpidfj5q4v6n4fm93.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query (_443._tcp.pastagacorporation.fr) sends a valid NSEC3 RR as result with the hashed query name "pclpid6lhh17ai2l5vmfvkuc0kuq4kf3" between the hashed NSEC3-owner "nncibov43baeek0ovmbmhd0ndbive4ho" and the hashed NextOwner "t3bvbuc1isj89flcgbqhi48t5h47mfme". So the zone confirmes the not-existence of that TLSA RR. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner nncibov43baeek0ovmbmhd0ndbive4ho.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	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 "977fj6tk5eekn0i8i3dsrcd2pou5jiec" (unhashed: *._tcp.pastagacorporation.fr) with the owner "8tqofg89d3qvdmbriiu2c2fr1ikqn0lp" and the NextOwner "j90vh1gm4c8c5bgb7e6atudfmr5o39dg". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 8tqofg89d3qvdmbriiu2c2fr1ikqn0lp.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "6l96oh78qa1mdqkji23do90t9iid48fv" equal the hashed NSEC3-owner "6l96oh78qa1mdqkji23do90t9iid48fv" and the hashed NextOwner "8tqofg89d3qvdmbriiu2c2fr1ikqn0lp". 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, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 6l96oh78qa1mdqkji23do90t9iid48fv.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	Status: Good. NoData-Proof required and found.

Zone: www.pastagacorporation.fr
www.pastagacorporation.fr	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 "4a7et20rpps5r7abb0sa052rdl3vcm20" between the hashed NSEC3-owner "3srtfff8n1dvcr60r7gp4jm0d30vhbah" and the hashed NextOwner "544nrg8uhr0lkdau2tj6qca8ovlo1gko". So the parent zone confirmes the not-existence of a DS RR. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner 3srtfff8n1dvcr60r7gp4jm0d30vhbah.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "6l96oh78qa1mdqkji23do90t9iid48fv" as Owner. That's the Hash of "pastagacorporation.fr" with the NextHashedOwnerName "8tqofg89d3qvdmbriiu2c2fr1ikqn0lp". So that domain name is the Closest Encloser of "www.pastagacorporation.fr". Opt-Out: False. Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 6l96oh78qa1mdqkji23do90t9iid48fv.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr


	The ClosestEncloser says, that "*.pastagacorporation.fr" with the Hash "bd00beksgqoqugpciduois7tcen5b8lf" 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 "8tqofg89d3qvdmbriiu2c2fr1ikqn0lp" and the Next Owner "j90vh1gm4c8c5bgb7e6atudfmr5o39dg", 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 8tqofg89d3qvdmbriiu2c2fr1ikqn0lp.pastagacorporation.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 29.12.2024, 08:43:51 +, Signature-Inception: 29.11.2024, 08:43:51 +, KeyTag 6813, Signer-Name: pastagacorporation.fr

3. Name Servers

Domain	Nameserver	NS-IP
www.pastagacorporation.fr	• dns19.ovh.net
pastagacorporation.fr	• dns19.ovh.net	213.251.188.139 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:4a8b::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	• ns19.ovh.net	213.251.128.139 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
	•	2001:41d0:1:198b::1 Roubaix/Hauts-de-France/France (FR) - OVH SAS	•
fr	• a.nic.fr
	• d.nic.fr / dns.ams.nic.fr		•
	• f.ext.nic.fr / s2.amx		•
	• g.ext.nic.fr / 5.ams.pch		•

4. SOA-Entries

Domain:	fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	fr
Zone-Name:	fr
Primary:	a.nic.fr
Mail:	dnsmaster.afnic.fr
Serial:	2240069084
Refresh:	3600
Retry:	1800
Expire:	1209600
TTL:	600
num Entries:	3

Domain:	pastagacorporation.fr
Zone-Name:	pastagacorporation.fr
Primary:	dns19.ovh.net
Mail:	tech.ovh.net
Serial:	2024112904
Refresh:	86400
Retry:	3600
Expire:	3600000
TTL:	60
num Entries:	4

Domain:	www.pastagacorporation.fr
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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://pastagacorporation.fr/ 51.83.72.179	302	https://pastagacorporation.fr/	0.060	A
Location: https://pastagacorporation.fr/
Cache-Control: no-cache
Content-Length: 0

• http://pastagacorporation.fr/ 2001:41d0:304:200::6673	302	https://pastagacorporation.fr/	0.053	A
Location: https://pastagacorporation.fr/
Cache-Control: no-cache
Content-Length: 0

• https://pastagacorporation.fr/ 51.83.72.179	-103		0.060	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://pastagacorporation.fr/ 2001:41d0:304:200::6673	-103		0.057	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• http://pastagacorporation.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 51.83.72.179 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	503	Html is minified: 101.89 % Other inline scripts (∑/total): 0/0	3.040	S
Service Unavailable
Visible Content:
Cache-Control: no-cache
Content-Type: text/html
Content-Length: 108

• http://pastagacorporation.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:304:200::6673 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	503	Html is minified: 101.89 % Other inline scripts (∑/total): 0/0	3.040	S
Service Unavailable
Visible Content:
Cache-Control: no-cache
Content-Type: text/html
Content-Length: 108

• https://51.83.72.179/ 51.83.72.179	-103		0.060	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://[2001:41d0:0304:0200:0000:0000:0000:6673]/ 2001:41d0:304:200::6673	-103		0.060	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

7. Comments

	1. General Results, most used to calculate the result
A	name "pastagacorporation.fr" is domain, public suffix is ".fr", top-level-domain is ".fr", top-level-domain-type is "country-code", Country is France, tld-manager is "Association Française pour le Nommage Internet en Coopération (A.F.N.I.C.)", num .fr-domains preloaded: 3770 (complete: 263653)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: pastagacorporation.fr has 2 different ip addresses (authoritative).
A	Good: Ipv4 and Ipv6 addresses per domain name found: pastagacorporation.fr has 1 ipv4, 1 ipv6 addresses
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	Good: No cookie sent via http.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain pastagacorporation.fr, 2 ip addresses.
	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 pastagacorporation.fr, 2 ip addresses.
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.pastagacorporation.fr
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: dns19.ovh.net, ns19.ovh.net, 2 Name Servers included in Delegation: dns19.ovh.net, ns19.ovh.net, 2 Name Servers included in 1 Zone definitions: dns19.ovh.net, ns19.ovh.net, 1 Name Servers listed in SOA.Primary: dns19.ovh.net.
A	Good: Only one SOA.Primary Name Server found.: dns19.ovh.net.
A	Good: SOA.Primary Name Server included in the delegation set.: dns19.ovh.net.
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: dns19.ovh.net, ns19.ovh.net
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: 2 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 Name Servers, 1 Top Level Domain: net
	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: ovh.net
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:198b:, 2001:41d0:0001:4a8b:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: a.nic.fr: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
	Nameserver doesn't pass all EDNS-Checks: d.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns.ams.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: dns19.ovh.net: 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
	http://pastagacorporation.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 51.83.72.179	503	Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://pastagacorporation.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:304:200::6673	503	Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
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: 58996 milliseconds, 58.996 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found

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

No CRT - CT-Log entries found

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns19.ovh.net, ns19.ovh.net

QNr.	Domain	Type	NS used
1	net	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	dns19.ovh.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net
	Answer: dns10.ovh.net 2001:41d0:1:4a81::1, 213.251.188.129
	Answer: dns11.ovh.net 2001:41d0:1:4a82::1, 213.251.188.130
	Answer: dns12.ovh.net 2001:41d0:1:4a83::1, 213.251.188.131
	Answer: dns13.ovh.net 2001:41d0:1:4a84::1, 213.251.188.132
	Answer: dns15.ovh.net 2001:41d0:1:4a86::1, 213.251.188.134
	Answer: ns10.ovh.net 2001:41d0:1:1981::1, 213.251.128.129
	Answer: ns11.ovh.net 2001:41d0:1:1982::1, 213.251.128.130
	Answer: ns12.ovh.net 2001:41d0:1:1983::1, 213.251.128.131
	Answer: ns13.ovh.net 2001:41d0:1:1984::1, 213.251.128.132
	Answer: ns15.ovh.net 2001:41d0:1:1986::1, 213.251.128.134
3	ns19.ovh.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net
	Answer: dns10.ovh.net 2001:41d0:1:4a81::1, 213.251.188.129
	Answer: dns11.ovh.net 2001:41d0:1:4a82::1, 213.251.188.130
	Answer: dns12.ovh.net 2001:41d0:1:4a83::1, 213.251.188.131
	Answer: dns13.ovh.net 2001:41d0:1:4a84::1, 213.251.188.132
	Answer: dns15.ovh.net 2001:41d0:1:4a86::1, 213.251.188.134
	Answer: ns10.ovh.net 2001:41d0:1:1981::1, 213.251.128.129
	Answer: ns11.ovh.net 2001:41d0:1:1982::1, 213.251.128.130
	Answer: ns12.ovh.net 2001:41d0:1:1983::1, 213.251.128.131
	Answer: ns13.ovh.net 2001:41d0:1:1984::1, 213.251.128.132
	Answer: ns15.ovh.net 2001:41d0:1:1986::1, 213.251.128.134
4	dns19.ovh.net: 213.251.188.139	A	dns10.ovh.net (2001:41d0:1:4a81::1)
5	dns19.ovh.net: 2001:41d0:1:4a8b::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)
6	ns19.ovh.net: 213.251.128.139	A	dns10.ovh.net (2001:41d0:1:4a81::1)
7	ns19.ovh.net: 2001:41d0:1:198b::1	AAAA	dns10.ovh.net (2001:41d0:1:4a81::1)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
pastagacorporation.fr	0		no CAA entry found	1	0
fr	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
pastagacorporation.fr	v=spf1 a include:mx.ovh.com ~all	ok	1
_acme-challenge.pastagacorporation.fr		Name Error - The domain name does not exist	1
_acme-challenge.pastagacorporation.fr.pastagacorporation.fr		Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
MX		pastagacorporation.fr	1	mx1.mail.ovh.net	0	3	ok
	A			188.165.36.237	0	1	ok
	CNAME				0	0	ok
MX		pastagacorporation.fr	5	mx2.mail.ovh.net	0	3	ok
	A			87.98.160.167	0	1	ok
	CNAME				0	0	ok
MX		pastagacorporation.fr	100	mx3.mail.ovh.net	0	3	ok
	A			91.121.53.175	0	1	ok
	CNAME				0	0	ok
SPF	TXT	pastagacorporation.fr		v=spf1 a include:mx.ovh.com ~all			ok
	TXT	mx.ovh.com		ptr:mail-out.ovh.net			4096	"ptr" is deprecated. Don't use it.
	A	pastagacorporation.fr		51.83.72.179			ok
	AAAA	pastagacorporation.fr		2001:41d0:304:200::6673			ok
	TXT	mx.ovh.com		v=spf1 ptr:mail-out.ovh.net ptr:mail.ovh.net ip4:8.33.137.105/32 ip4:192.99.77.81/32 ?all			ok
	TXT	mx.ovh.com		ptr:mail.ovh.net			4096	"ptr" is deprecated. Don't use it.

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=13e28ed5-e88c-4222-9e30-d37c853ac1fb

Last Result: https://check-your-website.server-daten.de/?q=pastagacorporation.fr - 2024-11-29 11:27: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=pastagacorporation.fr" target="_blank">Check this Site: pastagacorporation.fr</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=pastagacorporation.fr