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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
11.10.2019 22:11:22

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
lets-encrypt.infr.search.usa.gov	CNAME	lets-encrypt.search.gov	yes	1	0
	A	34.238.89.30 Ashburn/Virginia/United States (US) - Amazon.com, Inc. Hostname: ec2-34-238-89-30.compute-1.amazonaws.com	yes
www.lets-encrypt.infr.search.usa.gov		Name Error	yes	1	0

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	• 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 22545, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner gov., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.10.2019, 17:00:00 +, Signature-Inception: 11.10.2019, 16:00:00 +, KeyTag 22545, Signer-Name: (root)


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 7877, Flags 256


	Public Key with Algorithm 8, KeyTag 32795, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gov., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.10.2019, 21:47:31 +, Signature-Inception: 04.10.2019, 21:42:31 +, KeyTag 7698, Signer-Name: gov


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


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


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

Zone: usa.gov
usa.gov	2 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner usa.gov., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.10.2019, 16:10:07 +, Signature-Inception: 11.10.2019, 16:10:07 +, KeyTag 7877, Signer-Name: gov


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 6078, Flags 256


	Public Key with Algorithm 8, KeyTag 7474, Flags 256


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


	3 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner usa.gov., Algorithm: 8, 2 Labels, original TTL: 10800 sec, Signature-expiration: 10.11.2019, 16:39:29 +, Signature-Inception: 11.10.2019, 16:34:29 +, KeyTag 6078, Signer-Name: usa.gov


	RRSIG-Owner usa.gov., Algorithm: 8, 2 Labels, original TTL: 10800 sec, Signature-expiration: 10.11.2019, 16:39:29 +, Signature-Inception: 11.10.2019, 16:34:29 +, KeyTag 7474, Signer-Name: usa.gov


	RRSIG-Owner usa.gov., Algorithm: 8, 2 Labels, original TTL: 10800 sec, Signature-expiration: 10.11.2019, 16:39:29 +, Signature-Inception: 11.10.2019, 16:34:29 +, KeyTag 56804, Signer-Name: usa.gov


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


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


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


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


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

Zone: search.usa.gov
search.usa.gov	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 "gjrbatrf8dc6do0usotj9mrofpfc5gr6" between the hashed NSEC3-owner "gjrbatrf8dc6do0usotj9mrofpfc5gr6" and the hashed NextOwner "gpcsi4inh71htco18dbsvsqpesmu8a3k". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner gjrbatrf8dc6do0usotj9mrofpfc5gr6.usa.gov., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 10.11.2019, 16:39:29 +, Signature-Inception: 11.10.2019, 16:34:29 +, KeyTag 6078, Signer-Name: usa.gov


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "gjrbatrf8dc6do0usotj9mrofpfc5gr6" between the hashed NSEC3-owner "gjrbatrf8dc6do0usotj9mrofpfc5gr6" and the hashed NextOwner "gpcsi4inh71htco18dbsvsqpesmu8a3k". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner gjrbatrf8dc6do0usotj9mrofpfc5gr6.usa.gov., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 10.11.2019, 16:39:29 +, Signature-Inception: 11.10.2019, 16:34:29 +, KeyTag 7474, Signer-Name: usa.gov


	0 DNSKEY RR found




Zone: infr.search.usa.gov
infr.search.usa.gov	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: lets-encrypt.infr.search.usa.gov
lets-encrypt.infr.search.usa.gov	0 DS RR in the parent zone found

Zone: www.lets-encrypt.infr.search.usa.gov
www.lets-encrypt.infr.search.usa.gov	0 DS RR in the parent zone found

Zone: (root)
(root)	1 DS RR published


	• 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 22545, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner gov., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.10.2019, 17:00:00 +, Signature-Inception: 11.10.2019, 16:00:00 +, KeyTag 22545, Signer-Name: (root)


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 7877, Flags 256


	Public Key with Algorithm 8, KeyTag 32795, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gov., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.10.2019, 21:47:31 +, Signature-Inception: 04.10.2019, 21:42:31 +, KeyTag 7698, Signer-Name: gov


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


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


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

Zone: search.gov
search.gov	2 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner search.gov., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.10.2019, 16:10:07 +, Signature-Inception: 11.10.2019, 16:10:07 +, KeyTag 7877, Signer-Name: gov


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 1578, Flags 256


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


	Public Key with Algorithm 8, KeyTag 52398, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner search.gov., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 24.10.2019, 00:00:00 +, Signature-Inception: 03.10.2019, 00:00:00 +, KeyTag 19720, Signer-Name: search.gov


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


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


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

Zone: lets-encrypt.search.gov
lets-encrypt.search.gov	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 "7thucrpjfq9uh569a182erd3ci9mgo9q" between the hashed NSEC3-owner "7thucrpjfq9uh569a182erd3ci9mgo9q" and the hashed NextOwner "82cnpi310ma4t1bbtjoe5rfcdod8d129". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner 7thucrpjfq9uh569a182erd3ci9mgo9q.search.gov., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 24.10.2019, 00:00:00 +, Signature-Inception: 03.10.2019, 00:00:00 +, KeyTag 1578, Signer-Name: search.gov


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 34.238.89.30 Validated: RRSIG-Owner lets-encrypt.search.gov., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 24.10.2019, 00:00:00 +, Signature-Inception: 03.10.2019, 00:00:00 +, KeyTag 1578, Signer-Name: search.gov


	RRSIG Type 50, expiration 2019-10-24 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CNAME RR. Bitmap: A, RRSIG


	RRSIG Type 50, expiration 2019-10-24 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TXT RR. Bitmap: A, RRSIG


	RRSIG Type 50, expiration 2019-10-24 00:00:00 + validates the NSEC3 RR that proves the not-existence of the AAAA RR. Bitmap: A, RRSIG


	RRSIG Type 50, expiration 2019-10-24 00:00:00 + validates the NSEC3 RR that proves the not-existence of the TLSA RR. Bitmap: A, RRSIG


	RRSIG Type 50, expiration 2019-10-24 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CAA RR. Bitmap: A, RRSIG

3. Name Servers

Domain	Nameserver	NS-IP
www.lets-encrypt.infr.search.usa.gov	• ns-302.awsdns-37.com
infr.search.usa.gov	• ns-302.awsdns-37.com / 9d87422d137f8491cb37c193cce7355b -		•
search.usa.gov	• ns-1342.awsdns-39.org / 5c38236454b6df637a6b1473d418b951 -		•
	• ns-1717.awsdns-22.co.uk / a23e81034d2be401ba2f7a0db2693566 -		•
	• ns-302.awsdns-37.com / 083edb44120aafd07e53c75bb2456f87 -		•
	• ns-628.awsdns-14.net / a3f4c95fd4082dff4c6f2da186ae4a16 -		•
usa.gov	• dns.gsa.gov		•
	• dns2.gsa.gov		•
	• dns3.gsa.gov		•
	• dns4.gsa.gov		•
	• dns5.gsa.gov		•
gov	• a.gov-servers.net		•
	• b.gov-servers.net		•
	• c.gov-servers.net		•
	• d.gov-servers.net		•

lets-encrypt.search.gov	• ns1.search.gov / ns1.us-east-1.prod.infr.search.usa.gov	52.203.57.242 Ashburn/Virginia/United States (US) - Amazon.com, Inc.	•
search.gov	• ns1.search.gov / ns1.us-east-1.prod.infr.search.usa.gov		•
	T ns2.search.gov
	• ns3.search.gov / ns3.us-east-1.prod.infr.search.usa.gov		•
gov	• a.gov-servers.net		•
	• b.gov-servers.net		•
	• c.gov-servers.net		•
	• d.gov-servers.net		•

4. SOA-Entries

Domain:	gov
Zone-Name:
Primary:	a.gov-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1570813801
Refresh:	3600
Retry:	900
Expire:	1814400
TTL:	86400
num Entries:	4

Domain:	usa.gov
Zone-Name:
Primary:	dns.gsa.gov
Mail:	hostmaster.gsa.gov
Serial:	589826369
Refresh:	3600
Retry:	180
Expire:	1209600
TTL:	3600
num Entries:	5

Domain:	search.usa.gov
Zone-Name:
Primary:	ns-302.awsdns-37.com
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	4

Domain:	infr.search.usa.gov
Zone-Name:
Primary:	ns-302.awsdns-37.com
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	1

Domain:	www.lets-encrypt.infr.search.usa.gov
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1


Domain:	gov
Zone-Name:
Primary:	a.gov-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1570813801
Refresh:	3600
Retry:	900
Expire:	1814400
TTL:	86400
num Entries:	4

Domain:	search.gov
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	search.gov
Zone-Name:
Primary:	ns1.search.gov
Mail:	dns-master.search.gov
Serial:	2018021601
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	2

Domain:	lets-encrypt.search.gov
Zone-Name:
Primary:	ns1.search.gov
Mail:	dns-master.search.gov
Serial:	2018021601
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	1

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://lets-encrypt.infr.search.usa.gov/ 34.238.89.30	301	https://lets-encrypt.infr.search.usa.gov/ Html is minified: 100.00 %	0.237	A
Date: Fri, 11 Oct 2019 20:13:37 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
Location: https://lets-encrypt.infr.search.usa.gov/
Content-Length: 331
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://lets-encrypt.infr.search.usa.gov/ 34.238.89.30 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	200	Other inline scripts (∑/total): 0/0	3.917	A
small visible content (num chars: 0)
Date: Fri, 11 Oct 2019 20:13:38 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
Last-Modified: Fri, 11 Oct 2019 17:29:33 GMT
ETag: "0-594a5dc83eb23"
Accept-Ranges: bytes
Content-Length: 0
Connection: close
Content-Type: text/html

• http://lets-encrypt.infr.search.usa.gov/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.238.89.30 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://lets-encrypt.infr.search.usa.gov/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	0.240	A
Visible Content: Moved Permanently The document has moved here . Apache Server at lets-encrypt.infr.search.usa.gov Port 80
Date: Fri, 11 Oct 2019 20:13:41 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
Location: https://lets-encrypt.infr.search.usa.gov/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 400
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://lets-encrypt.infr.search.usa.gov/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	3.590	A
Not Found
Visible Content: Not Found The requested URL was not found on this server. Apache Server at lets-encrypt.infr.search.usa.gov Port 443
Date: Fri, 11 Oct 2019 20:13:42 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
Content-Length: 279
Connection: close
Content-Type: text/html; charset=iso-8859-1

7. Comments

	1. General Results, most used to calculate the result
A	name "lets-encrypt.infr.search.usa.gov" is subdomain, public suffix is "gov", top-level-domain-type is "sponsored", tld-manager is "General Services Administration Attn: QTDC, 2E08 (.gov Domain Registration)"
A	Good: All ip addresses are public 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: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: non-www is preferred
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS max-age is long enough, 31536000 seconds = 365 days
A	Good: HSTS has includeSubdomains - directive
A	Good: HSTS has preload directive
	Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should immediately add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
	https://lets-encrypt.infr.search.usa.gov/ 34.238.89.30			Url with incomplete Content-Type - header - missing charset
A	http://lets-encrypt.infr.search.usa.gov/ 34.238.89.30	301	https://lets-encrypt.infr.search.usa.gov/	Correct redirect http - https with the same domain name
X	Fatal error: Nameserver doesn't support TCP connection: ns2.search.gov: Timeout
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
	3. DNS- and NameServer - Checks
A	Good: Nameserver supports TCP connections: 1 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 1 good Nameserver
X	Nameserver Timeout checking Echo Capitalization: ns2.search.gov
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns1.search.gov: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns1.us-east-1.prod.infr.search.usa.gov). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns1.search.gov / 52.203.57.242: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns1.us-east-1.prod.infr.search.usa.gov). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.search.gov: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns3.search.gov: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns3.us-east-1.prod.infr.search.usa.gov). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns-302.awsdns-37.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: 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.
	https://lets-encrypt.infr.search.usa.gov/ 34.238.89.30	200		Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
A	Good: No https + http status 200 with inline CSS / JavaScript found
	https://lets-encrypt.infr.search.usa.gov/ 34.238.89.30	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.
	https://lets-encrypt.infr.search.usa.gov/ 34.238.89.30	200		Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
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
	http://lets-encrypt.infr.search.usa.gov/ 34.238.89.30	301		Warning: HSTS header sent via http has no effect
	https://lets-encrypt.infr.search.usa.gov/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	3.590 seconds	Warning: 404 needs more then one second
A	Duration: 154763 milliseconds, 154.763 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

lets-encrypt.infr.search.usa.gov

34.238.89.30

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

lets-encrypt.infr.search.usa.gov

34.238.89.30

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

no http/2 via ALPN

no Tls.1.2
no Tls.1.1
no Tls.1.0

no http/2 via ALPN

no Tls.1.2
no Tls.1.1
no Tls.1.0

Chain - incomplete	1	CN=lets-encrypt.infr.search.usa.gov
	2	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

lets-encrypt.infr.search.usa.gov

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

lets-encrypt.infr.search.usa.gov

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

no http/2 via ALPN

no Tls.1.2
no Tls.1.1
no Tls.1.0

no http/2 via ALPN

no Tls.1.2
no Tls.1.1
no Tls.1.0

Chain - incomplete	1	CN=lets-encrypt.infr.search.usa.gov
	2	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

9. Certificates

CN=lets-encrypt.infr.search.usa.gov

11.10.2019

09.01.2020
1793 days expired

lets-encrypt.infr.search.usa.gov - 1 entry

CN=lets-encrypt.infr.search.usa.gov

11.10.2019

09.01.2020
1793 days expired

lets-encrypt.infr.search.usa.gov - 1 entry

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	030140E5655B1B3C812B1BC16EEF6F4A98A2
Thumbprint:	9BDC845BF731A2F02714EE5B282EAD015B7765AA
SHA256 / Certificate:	U1WbETIXWFn0Vtoh96k9IeCJrhUbh8tPJnwFgqAOzmc=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	aab056aa800d329c9afc7b9ceb5c3d3749ab2ad8bc0017dc78ad9d0857f9cd20
SHA256 hex / Subject Public Key Information (SPKI):	aab056aa800d329c9afc7b9ceb5c3d3749ab2ad8bc0017dc78ad9d0857f9cd20
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.int-x3.letsencrypt.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)

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1360 days expired

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1360 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0A0141420000015385736A0B85ECA708
Thumbprint:	E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:	JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):	25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

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

30.09.2000

30.09.2021
1163 days expired

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

30.09.2000

30.09.2021
1163 days expired

Keyalgorithm	RSA 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:

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

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.

Small Code update, wait one minute

13. Nameserver - IP-Adresses

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

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

14. CAA - Entries

Domainname	flag	Value	∑ Queries
lets-encrypt.infr.search.usa.gov			1
lets-encrypt.search.gov	0	no CAA entry found	1
infr.search.usa.gov	0	no CAA entry found	1
search.usa.gov	0	no CAA entry found	1
search.gov	0	no CAA entry found	1
usa.gov	0	no CAA entry found	1
gov	0	no CAA entry found	1
	0	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
search.gov	v=spf1 include:amazonses.com include:mail.zendesk.com include:_spf.google.com -all	ok	1
infr.search.usa.gov	v=spf1 -all	ok	1
lets-encrypt.search.gov		ok	1
lets-encrypt.infr.search.usa.gov			1
_acme-challenge.lets-encrypt.search.gov		Name Error - The domain name does not exist	1
_acme-challenge.lets-encrypt.infr.search.usa.gov		Name Error - The domain name does not exist	1
_acme-challenge.lets-encrypt.search.gov.search.gov		Name Error - The domain name does not exist	1
_acme-challenge.lets-encrypt.search.gov.lets-encrypt.search.gov		Name Error - The domain name does not exist	1
_acme-challenge.lets-encrypt.infr.search.usa.gov.infr.search.usa.gov		Name Error - The domain name does not exist	1
_acme-challenge.lets-encrypt.infr.search.usa.gov.lets-encrypt.infr.search.usa.gov		Name Error - The domain name does not exist	1

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=3d80e592-d6bf-44cf-9ec9-24a53f584f66

Last Result: https://check-your-website.server-daten.de/?q=lets-encrypt.infr.search.usa.gov - 2019-10-11 22:11:22

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

<a href="https://check-your-website.server-daten.de/?q=lets-encrypt.infr.search.usa.gov" target="_blank">Check this Site: lets-encrypt.infr.search.usa.gov</a>

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

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

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

6. Url-Checks

7. Comments

1. General Results, most used to calculate the result

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

3. DNS- and NameServer - Checks

4. Content- and Performance-critical Checks

8. Connections

9. Certificates

10. Last Certificates - Certificate Transparency Log Check

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

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

11. Html-Content - Entries

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

13. Nameserver - IP-Adresses

14. CAA - Entries

15. TXT - Entries

16. DomainService - Entries

17. Cipher Suites

18. Portchecks