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

...

skip EDNS-Check

skip Content-Check

check links

Tls-Protocol error

Checked:
10.05.2025 03:16:53

Older results

N - 08.02.2025 02:38:26

N - 06.02.2025 01:57:04

N - 04.02.2025 15:48:52

N - 15.12.2023 02:26:41

X - 03.08.2023 15:19:00

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
thewwwthing.com	A	13.248.213.45 Toronto/Ontario/Canada (CA) - Amazon.com, Inc. Hostname: a67c48129651a0940.awsglobalaccelerator.com	yes	2	0
	A	76.223.67.189 Seattle/Washington/United States (US) - Amazon.com, Inc. Hostname: a67c48129651a0940.awsglobalaccelerator.com	yes	2	0
	AAAA		yes
www.thewwwthing.com	CNAME	thewwwthing.com	yes	1	0
	A	13.248.213.45 Toronto/Ontario/Canada (CA) - Amazon.com, Inc. Hostname: a67c48129651a0940.awsglobalaccelerator.com	yes
	A	76.223.67.189 Seattle/Washington/United States (US) - Amazon.com, Inc. Hostname: a67c48129651a0940.awsglobalaccelerator.com	yes
*.thewwwthing.com	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	3 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2025, 20:00:00 +, Signature-Inception: 09.05.2025, 19:00:00 +, KeyTag 53148, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 40097, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.05.2025, 14:02:35 +, Signature-Inception: 02.05.2025, 13:57:35 +, KeyTag 19718, Signer-Name: com


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


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

Zone: thewwwthing.com
thewwwthing.com	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 "e1lbfqnecc7tnpou5pksnnlcjvn0vigd" between the hashed NSEC3-owner "e1lb7huol2cc6e812ahopnisivf6ph8d" and the hashed NextOwner "e1lbg7e03fhk47032r85cv6hkufaa7go". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e1lb7huol2cc6e812ahopnisivf6ph8d.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 13.05.2025, 02:04:24 +, Signature-Inception: 06.05.2025, 00:54:24 +, KeyTag 40097, Signer-Name: com


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "thewwwthing.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 15.05.2025, 00:25:55 +, Signature-Inception: 07.05.2025, 23:15:55 +, KeyTag 40097, Signer-Name: com


	0 DNSKEY RR found




Zone: www.thewwwthing.com
www.thewwwthing.com	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
thewwwthing.com	• ns49.domaincontrol.com / hex:0D 70 31 33	97.74.104.25 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:2182::19 Chicago/Illinois/United States (US) - Host Europe GmbH	•
	• ns50.domaincontrol.com / hex:0D 70 31 32	173.201.72.25 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:2282::19 Chicago/Illinois/United States (US) - Host Europe GmbH	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-eltxl1		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746839785
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	6

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746839800
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	7

Domain:	thewwwthing.com
Zone-Name:	thewwwthing.com
Primary:	ns49.domaincontrol.com
Mail:	dns.jomax.net
Serial:	2025050400
Refresh:	28800
Retry:	7200
Expire:	604800
TTL:	600
num Entries:	4

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://thewwwthing.com/ 13.248.213.45	200	Html is minified: 278.05 %	0.207	H
Date: Sat, 10 May 2025 01:17:34 GMT
Content-Type: text/html
Content-Length: 114

• http://thewwwthing.com/ 76.223.67.189	200	Html is minified: 278.05 %	0.247	H
Date: Sat, 10 May 2025 01:17:34 GMT
Content-Type: text/html
Content-Length: 114

• http://www.thewwwthing.com/ 13.248.213.45	200	Html is minified: 278.05 %	0.120	H
Date: Sat, 10 May 2025 01:17:34 GMT
Content-Type: text/html
Content-Length: 114

• http://www.thewwwthing.com/ 76.223.67.189	200	Html is minified: 278.05 %	0.120	H
Date: Sat, 10 May 2025 01:17:34 GMT
Content-Type: text/html
Content-Length: 114

• https://thewwwthing.com/ 13.248.213.45	-103		0.260	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

• https://thewwwthing.com/ 76.223.67.189	-103		0.324	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

• https://www.thewwwthing.com/ 13.248.213.45	-103		0.267	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

• https://www.thewwwthing.com/ 76.223.67.189	-103		0.324	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

• http://thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.213.45 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	403	Html is minified: 101.09 % Other inline scripts (∑/total): 0/0	0.130	M
Forbidden
Visible Content:
Cache-Control: no-cache
Content-Length: 93
Content-Type: text/html

• http://thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.67.189 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	403	Html is minified: 101.09 % Other inline scripts (∑/total): 0/0	0.113	M
Forbidden
Visible Content:
Cache-Control: no-cache
Content-Length: 93
Content-Type: text/html

• http://www.thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.213.45 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	403	Html is minified: 101.09 % Other inline scripts (∑/total): 0/0	0.117	M
Forbidden
Visible Content:
Cache-Control: no-cache
Content-Length: 93
Content-Type: text/html

• http://www.thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.67.189 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	403	Html is minified: 101.09 % Other inline scripts (∑/total): 0/0	0.123	M
Forbidden
Visible Content:
Cache-Control: no-cache
Content-Length: 93
Content-Type: text/html

• https://13.248.213.45/ 13.248.213.45	-103		0.240	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

• https://76.223.67.189/ 76.223.67.189	-103		0.233	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

7. Comments

	1. General Results, most used to calculate the result
A	name "thewwwthing.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 105479 (complete: 270180)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: thewwwthing.com has 2 different ip addresses (authoritative).
A	Good: Minimal 2 ip addresses per domain name found: www.thewwwthing.com has 2 different ip addresses (authoritative).
	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: thewwwthing.com has no ipv6 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: www.thewwwthing.com has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
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.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (8 urls)
	http://thewwwthing.com/ 13.248.213.45		Url with incomplete Content-Type - header - missing charset
	http://thewwwthing.com/ 76.223.67.189		Url with incomplete Content-Type - header - missing charset
	http://www.thewwwthing.com/ 13.248.213.45		Url with incomplete Content-Type - header - missing charset
	http://www.thewwwthing.com/ 76.223.67.189		Url with incomplete Content-Type - header - missing charset
	http://thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.213.45		Url with incomplete Content-Type - header - missing charset
	http://thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.67.189		Url with incomplete Content-Type - header - missing charset
	http://www.thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.213.45		Url with incomplete Content-Type - header - missing charset
	http://www.thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.67.189		Url with incomplete Content-Type - header - missing charset
H	Fatal error: No https - result with http-status 200, no encryption
H	Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
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 thewwwthing.com, 2 ip addresses.
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 www.thewwwthing.com, 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 thewwwthing.com, 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 www.thewwwthing.com, 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.thewwwthing.com
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 26 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 26 Queries complete, 26 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 13.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns49.domaincontrol.com, ns50.domaincontrol.com, 2 Name Servers included in Delegation: ns49.domaincontrol.com, ns50.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns49.domaincontrol.com, ns50.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns49.domaincontrol.com.
A	Good: Only one SOA.Primary Name Server found.: ns49.domaincontrol.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns49.domaincontrol.com.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns49.domaincontrol.com, ns50.domaincontrol.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 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: 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: domaincontrol.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.72., 97.74.104.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:2182:, 2603:0005:2282:, 2 different subnets (first four blocks): 2603:0005:2182:0000:, 2603:0005:2282:0000:
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
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
	4. Content- and Performance-critical Checks
	http://thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.213.45	403	Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.67.189	403	Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 13.248.213.45	403	Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.thewwwthing.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.67.189	403	Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not 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: 89337 milliseconds, 89.337 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)

Issuer				last 7 days	active	num Certs
CN=R11, O=Let's Encrypt, C=US				0	1	2
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	0	2
CN=R3, O=Let's Encrypt, C=US				0	0	1
CN=R10, O=Let's Encrypt, C=US				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
9874722744 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-03-22 14:30:56	2025-06-20 14:30:55	thewwwthing.com - 1 entries
9275664801 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-01-20 21:03:23	2025-04-20 21:03:22	thewwwthing.com - 1 entries
8635003697 leaf cert	CN=R10, O=Let's Encrypt, C=US	2024-11-11 17:59:19	2025-02-09 17:59:18	thewwwthing.com - 1 entries
6127921015 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-11-04 16:39:37	2024-02-02 16:39:36	thewwwthing.com - 1 entries
4757706477 precert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2023-01-31 10:55:26	2023-09-06 16:48:26	thewwwthing.com, www.thewwwthing.com - 2 entries
4146893313 precert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2022-09-06 16:48:26	2023-09-06 16:48:26	thewwwthing.com, www.thewwwthing.com - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=R11, O=Let's Encrypt, C=US				0	1	3
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	3
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	0	2
CN=R10, O=Let's Encrypt, C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
17319503798 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-03-22 13:30:56	2025-06-20 12:30:55	thewwwthing.com 1 entries
16694836747 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-01-20 20:03:23	2025-04-20 19:03:22	thewwwthing.com 1 entries
15380516480 leaf cert	CN=R10, O=Let's Encrypt, C=US	2024-11-11 16:59:19	2025-02-09 16:59:18	thewwwthing.com 1 entries
14415283224 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-09-03 13:39:43	2024-12-02 14:39:42	thewwwthing.com 1 entries
10997269730 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-11-04 15:39:37	2024-02-02 15:39:36	thewwwthing.com 1 entries
10178209190 precert	CN=R3, O=Let's Encrypt, C=US	2023-08-15 06:27:31	2023-11-13 07:27:30	thewwwthing.com 1 entries
10299447461 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-08-15 06:24:59	2023-11-13 07:24:58	www.thewwwthing.com 1 entries
8543027058 precert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2023-01-31 09:55:26	2023-09-06 14:48:26	thewwwthing.com, www.thewwwthing.com 2 entries
7486018175 precert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2022-09-06 14:48:26	2023-09-06 14:48:26	thewwwthing.com, www.thewwwthing.com 2 entries

11. Html-Content - Entries

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

12. Html-Parsing via https://validator.w3.org/nu/

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: ns49.domaincontrol.com, ns50.domaincontrol.com

QNr.	Domain	Type	NS used
1	com	NS	f.root-servers.net (2001:500:2f::f)
	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	ns49.domaincontrol.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
	Answer: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
3	ns50.domaincontrol.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
	Answer: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
4	net	NS	k.root-servers.net (2001:7fd::1)
	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
5	a1-245.akam.net	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
6	a11-64.akam.net	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
7	a20-65.akam.net	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
8	a6-66.akam.net	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
9	a8-67.akam.net	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
10	a9-67.akam.net	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
11	a1-245.akam.net: 193.108.91.245	A	a1-67.akam.net (2600:1401:2::43)
12	a1-245.akam.net: 2600:1401:2::f5	AAAA	a1-67.akam.net (2600:1401:2::43)
13	a11-64.akam.net: 84.53.139.64	A	a1-67.akam.net (2600:1401:2::43)
14	a11-64.akam.net: 2600:1480:1::40	AAAA	a1-67.akam.net (2600:1401:2::43)
15	a20-65.akam.net: 95.100.175.65	A	a1-67.akam.net (2600:1401:2::43)
16	a20-65.akam.net: 2a02:26f0:67::41	AAAA	a1-67.akam.net (2600:1401:2::43)
17	a6-66.akam.net: 23.211.133.66	A	a1-67.akam.net (2600:1401:2::43)
18	a6-66.akam.net: 2600:1401:1::42	AAAA	a1-67.akam.net (2600:1401:2::43)
19	a8-67.akam.net: 2.16.40.67	A	a1-67.akam.net (2600:1401:2::43)
20	a8-67.akam.net: 2600:1403:a::43	AAAA	a1-67.akam.net (2600:1401:2::43)
21	a9-67.akam.net: 184.85.248.67	A	a1-67.akam.net (2600:1401:2::43)
22	a9-67.akam.net: 2a02:26f0:117::43	AAAA	a1-67.akam.net (2600:1401:2::43)
23	ns49.domaincontrol.com: 97.74.104.25	A	a1-245.akam.net (2600:1401:2::f5)
24	ns49.domaincontrol.com: 2603:5:2182::19	AAAA	a1-245.akam.net (2600:1401:2::f5)
25	ns50.domaincontrol.com: 173.201.72.25	A	a1-245.akam.net (2600:1401:2::f5)
26	ns50.domaincontrol.com: 2603:5:2282::19	AAAA	a1-245.akam.net (2600:1401:2::f5)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries
www.thewwwthing.com	5	issue	letsencrypt.org	1
thewwwthing.com	5	issue	letsencrypt.org	1
com	0		no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
thewwwthing.com	apple-domain=sllobg970CHPjj7G	ok	1
thewwwthing.com	v=spf1 include:spf.protection.outlook.com -all	ok	1
www.thewwwthing.com	apple-domain=sllobg970CHPjj7G	ok	1
www.thewwwthing.com	v=spf1 include:spf.protection.outlook.com -all	ok	1
_acme-challenge.thewwwthing.com		Name Error - The domain name does not exist	1
_acme-challenge.www.thewwwthing.com		Name Error - The domain name does not exist	1
_acme-challenge.thewwwthing.com.thewwwthing.com		Name Error - The domain name does not exist	1
_acme-challenge.www.thewwwthing.com.thewwwthing.com		Name Error - The domain name does not exist	1
_acme-challenge.www.thewwwthing.com.www.thewwwthing.com		Name Error - The domain name does not exist	1

16. DomainService - Entries

Type	Domain	Pref	Value	DNS-error	num Answers	Status	Description
SPF	TXT	thewwwthing.com		v=spf1 include:spf.protection.outlook.com -all			ok
	TXT	spf.protection.outlook.com		v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all			ok

Type

Domain

Pref

Value

DNS-error

num Answers

Status

Description

SPF

TXT

thewwwthing.com

v=spf1 include:spf.protection.outlook.com -all

TXT

spf.protection.outlook.com

v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all

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=98dee4e0-e1f9-41bd-8464-0d515817913d

Last Result: https://check-your-website.server-daten.de/?q=thewwwthing.com - 2025-05-10 03:16:53

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

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