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

...

skip EDNS-Check

skip Content-Check

check links

Tls-Protocol error

Checked:
13.11.2025 20:58:39

Older results

P - 09.11.2025 16:52:32

P - 09.11.2025 04:32:09

P - 04.10.2025 23:58:44

P - 09.09.2025 21:33:40

P - 27.09.2024 02:31:57

P - 06.09.2024 20:25:15

P - 02.09.2024 21:07:55

P - 06.08.2024 01:47:28

P - 13.07.2024 18:08:11

P - 05.07.2024 22:53:53

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
odenfull.co	A	69.197.129.178 Kansas City/Missouri/United States (US) - WholeSale Internet No Hostname found	yes	2	0
	AAAA		yes
www.odenfull.co	CNAME	odenfull.co	yes	1	0
	A	69.197.129.178 Kansas City/Missouri/United States (US) - WholeSale Internet No Hostname found	yes
*.odenfull.co	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 61809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 62110, DigestType 2 and Digest SFfuGoXmYckhVq0JtAE52ufVvjfRF6EiMonw4gz51lQ=


	DS with Algorithm 8, KeyTag 7786, DigestType 2 and Digest 64T4ZMvobpE3ltLI3YGTOqLJS7z7c0GaQiULxGULCBs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.11.2025, 17:00:00 +, Signature-Inception: 13.11.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)


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


	4 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 16855, Flags 256


	Public Key with Algorithm 8, KeyTag 19065, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 25.11.2025, 13:55:28 +, Signature-Inception: 26.10.2025, 12:25:28 +, KeyTag 7786, Signer-Name: co


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


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

Zone: odenfull.co
odenfull.co	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 "jeo4a50mabt53fu7n7kk3dj800he567v" between the hashed NSEC3-owner "jenf19fquup47dhgoptm7l90kb13cq89" and the hashed NextOwner "jeoah70t1473utopqnp49rp7v9iiq30q". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner jenf19fquup47dhgoptm7l90kb13cq89.co., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 25.11.2025, 15:55:10 +, Signature-Inception: 26.10.2025, 14:25:10 +, KeyTag 16855, Signer-Name: co


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ldc0c7m112348qmhs09hokrvkepgubv6" as Owner. That's the Hash of "co" with the NextHashedOwnerName "ldc79n10ost1vrasudtlfi9bqh4dd95s". So that domain name is the Closest Encloser of "odenfull.co". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ldc0c7m112348qmhs09hokrvkepgubv6.co., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 25.11.2025, 13:55:28 +, Signature-Inception: 26.10.2025, 12:25:28 +, KeyTag 16855, Signer-Name: co


	0 DNSKEY RR found




Zone: www.odenfull.co
www.odenfull.co	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
odenfull.co	• ns49.domaincontrol.com / hex:0D 70 31 33	97.74.104.25 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:2182::19 New York/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 New York/United States (US) - Host Europe GmbH	•
co	• a.registrydns.co / PGXL-PS5KRW-2C7ZTP		•
	• b.registrydns.co / CKQV-6AF162-DWW7G4		•
	• c.registrydns.co / PGXL-PS5KRW-2C7ZTP		•
	• d.registrydns.co / CKQV-6AF162-DWW7G4		•
	• ns0.centralnic.net

4. SOA-Entries

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

Domain:	co
Zone-Name:	co
Primary:	ns0.centralnic.net
Mail:	hostmaster.centralnic.net
Serial:	1759485634
Refresh:	900
Retry:	1800
Expire:	6048000
TTL:	3600
num Entries:	4

Domain:	odenfull.co
Zone-Name:	odenfull.co
Primary:	ns49.domaincontrol.com
Mail:	dns.jomax.net
Serial:	2025061600
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://odenfull.co:2086/ 69.197.129.178 No Compression used - 491 / 635 - 77.32 % possible	200	Html is minified: 137.45 %	0.233	H
Server: nginx
Date: Thu, 13 Nov 2025 19:59:05 GMT
Connection: keep-alive
ETag: "615dc84b-27b"
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 635
Last-Modified: Wed, 06 Oct 2021 16:01:15 GMT

• http://www.odenfull.co:2086/ 69.197.129.178 No Compression used - 491 / 635 - 77.32 % possible	200	Html is minified: 137.45 %	0.137	H
Server: nginx
Date: Thu, 13 Nov 2025 19:59:05 GMT
Connection: keep-alive
ETag: "615dc84b-27b"
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 635
Last-Modified: Wed, 06 Oct 2021 16:01:15 GMT

• https://odenfull.co:2086/ 69.197.129.178	-103		0.270	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

• https://www.odenfull.co:2086/ 69.197.129.178	-103		0.260	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

• http://odenfull.co:2086/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.197.129.178 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 110.61 % Other inline scripts (∑/total): 0/0	0.140	A
Not Found
Visible Content:
Server: nginx
Date: Thu, 13 Nov 2025 19:59:05 GMT
Connection: keep-alive
Content-Type: text/html
Content-Length: 146

• http://www.odenfull.co:2086/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.197.129.178 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 110.61 % Other inline scripts (∑/total): 0/0	0.133	A
Not Found
Visible Content:
Server: nginx
Date: Thu, 13 Nov 2025 19:59:06 GMT
Connection: keep-alive
Content-Type: text/html
Content-Length: 146

• https://69.197.129.178:2086/ 69.197.129.178	-103		0.263	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

7. Comments

	1. General Results, most used to calculate the result
A	name "odenfull.co" is domain, public suffix is ".co", top-level-domain is ".co", top-level-domain-type is "country-code", Country is Colombia, tld-manager is ".CO Internet S.A.S.", num .co-domains preloaded: 2307 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: odenfull.co has only one ip address.
	Warning: Only one ip address found: www.odenfull.co has only one ip address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: odenfull.co 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.odenfull.co 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 (4 urls)
	http://odenfull.co:2086/ 69.197.129.178	Url with incomplete Content-Type - header - missing charset
	http://www.odenfull.co:2086/ 69.197.129.178	Url with incomplete Content-Type - header - missing charset
	http://odenfull.co:2086/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.197.129.178	Url with incomplete Content-Type - header - missing charset
	http://www.odenfull.co:2086/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.197.129.178	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.
	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 odenfull.co, 1 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.odenfull.co, 1 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.odenfull.co
	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
	Nameserver doesn't pass all EDNS-Checks: a.registrydns.co: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: c.registrydns.co: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.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
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.
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: 37580 milliseconds, 37.580 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=R3, O=Let's Encrypt, C=US				0	0	7
CN=R10, O=Let's Encrypt, C=US				0	0	5
CN=R11, O=Let's Encrypt, C=US				0	0	4
CN=E6, O=Let's Encrypt, C=US				0	0	2
CN=R13, O=Let's Encrypt, C=US				0	1	1
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	1	1
CN=E5, O=Let's Encrypt, C=US				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
11875166444 leaf cert	CN=R13, O=Let's Encrypt, C=US	2025-09-14 17:51:48	2025-12-13 17:51:47	odenfull.co - 1 entries
10779081781 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-06-16 18:38:47	2025-09-14 18:38:46	odenfull.co - 1 entries
10775722575 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-06-16 10:53:44	2025-09-14 10:53:43	odenfull.co - 1 entries
10758825317 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-06-14 18:43:41	2025-09-12 18:43:40	odenfull.co - 1 entries
10758662786 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-06-14 18:16:50	2025-09-12 18:16:49	maxximtv.xyz, odenfull.co - 2 entries
10758015641 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-06-14 16:32:46	2025-09-12 16:32:45	maxximtv.xyz, odenfull.co - 2 entries
10757447202 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-06-14 15:13:44	2025-09-12 15:13:43	maxximtv.xyz, odenfull.co - 2 entries
10735068173 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-06-12 13:25:43	2025-09-10 13:25:42	odenfull.co - 1 entries
10734666316 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-06-12 12:33:47	2025-09-10 12:33:46	odenfull.co - 1 entries
10730736939 leaf cert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2025-06-12 05:04:58	2026-06-12 05:04:58	odenfull.co - 1 entries
8170861324 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-09-13 05:13:39	2024-12-12 05:13:38	odenfull.co - 1 entries
8156344100 leaf cert	CN=R10, O=Let's Encrypt, C=US	2024-09-11 04:18:41	2024-12-10 04:18:40	odenfull.co - 1 entries
7602433613 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-06-29 06:15:07	2024-09-27 06:15:06	odenfull.co - 1 entries
7598483329 leaf cert	CN=R10, O=Let's Encrypt, C=US	2024-06-28 16:39:15	2024-09-26 16:39:14	odenfull.co - 1 entries
7124044140 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-04-14 04:57:33	2024-07-13 04:57:32	odenfull.co - 1 entries
7098158559 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-04-10 04:54:37	2024-07-09 04:54:36	odenfull.co - 1 entries
7098146489 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-04-10 04:52:27	2024-07-09 04:52:26	odenfull.co - 1 entries
7097122312 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-04-10 00:37:17	2024-07-09 00:37:16	maxximtv.xyz, odenfull.co, pelisyseriespty.xyz - 3 entries
6876149385 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-03-05 13:41:24	2024-06-03 13:41:23	maxximtv.xyz, odenfull.co, pelisyseriespty.xyz - 3 entries
6795966607 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-21 14:19:15	2024-05-21 14:19:14	odenfull.co - 1 entries
6784625646 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-19 17:23:16	2024-05-19 17:23:15	odenfull.co, panel.maxximtv.xyz, panel.pelisyseriespty.xyz - 3 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=R3, O=Let's Encrypt, C=US				0 /0 new	0	7
CN=R10, O=Let's Encrypt, C=US				0	0	4
CN=R11, O=Let's Encrypt, C=US				0	0	4
CN=E6, O=Let's Encrypt, C=US				0	0	4
CN=WE1, O=Google Trust Services, C=US				0	0	2
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	1	1
CN=R13, O=Let's Encrypt, C=US				0	1	1
CN=E5, O=Let's Encrypt, C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
21017658765 leaf cert	CN=R13, O=Let's Encrypt, C=US	2025-09-14 15:51:48	2025-12-13 16:51:47	odenfull.co 1 entries
19058844767 precert	CN=R11, O=Let's Encrypt, C=US	2025-06-16 16:38:47	2025-09-14 16:38:46	odenfull.co 1 entries
19052872698 precert	CN=R10, O=Let's Encrypt, C=US	2025-06-16 08:53:44	2025-09-14 08:53:43	odenfull.co 1 entries
19022254233 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-06-14 16:43:41	2025-09-12 16:43:40	odenfull.co 1 entries
19021960358 precert	CN=E6, O=Let's Encrypt, C=US	2025-06-14 16:16:50	2025-09-12 16:16:49	maxximtv.xyz, odenfull.co 2 entries
19020759756 precert	CN=E6, O=Let's Encrypt, C=US	2025-06-14 14:32:46	2025-09-12 14:32:45	maxximtv.xyz, odenfull.co 2 entries
19020286869 precert	CN=R11, O=Let's Encrypt, C=US	2025-06-14 13:13:44	2025-09-12 13:13:43	maxximtv.xyz, odenfull.co 2 entries
18978658164 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-06-12 11:25:43	2025-09-10 11:25:42	odenfull.co 1 entries
18977947637 precert	CN=R10, O=Let's Encrypt, C=US	2025-06-12 10:33:47	2025-09-10 10:33:46	odenfull.co 1 entries
18970907589 precert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2025-06-12 03:04:58	2026-06-12 03:04:58	odenfull.co 1 entries
18682966480 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-05-28 22:57:20	2025-08-26 22:57:19	*.odenfull.co, odenfull.co 2 entries
18667748377 precert	CN=WE1, O=Google Trust Services, C=US	2025-05-28 02:33:23	2025-08-26 03:31:53	*.odenfull.co, odenfull.co 2 entries
18490254641 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-05-18 23:16:46	2025-08-16 23:16:45	odenfull.co 1 entries
17505624501 precert	CN=E6, O=Let's Encrypt, C=US	2025-03-30 02:27:07	2025-06-28 02:27:06	*.odenfull.co, odenfull.co 2 entries
17504843677 precert	CN=WE1, O=Google Trust Services, C=US	2025-03-30 01:36:43	2025-06-28 02:35:25	*.odenfull.co, odenfull.co 2 entries
13559236332 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-06-29 04:15:07	2024-09-27 04:15:06	odenfull.co 1 entries
13552218167 leaf cert	CN=R10, O=Let's Encrypt, C=US	2024-06-28 14:39:15	2024-09-26 14:39:14	odenfull.co 1 entries
12719455293 precert	CN=R3, O=Let's Encrypt, C=US	2024-04-14 02:57:33	2024-07-13 02:57:32	odenfull.co 1 entries
12674866690 precert	CN=R3, O=Let's Encrypt, C=US	2024-04-10 02:54:37	2024-07-09 02:54:36	odenfull.co 1 entries
12674852813 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-04-10 02:52:27	2024-07-09 02:52:26	odenfull.co 1 entries
12673065742 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-04-09 22:37:17	2024-07-08 22:37:16	maxximtv.xyz, odenfull.co, pelisyseriespty.xyz 3 entries
12283226009 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-03-05 12:41:24	2024-06-03 11:41:23	maxximtv.xyz, odenfull.co, pelisyseriespty.xyz 3 entries
12148091730 precert	CN=R3, O=Let's Encrypt, C=US	2024-02-21 13:19:15	2024-05-21 12:19:14	odenfull.co 1 entries
12128887292 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-19 16:23:16	2024-05-19 15:23:15	odenfull.co, panel.maxximtv.xyz, panel.pelisyseriespty.xyz 3 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	l.root-servers.net (2001:500:9f::42)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	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: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
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: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
4	net	NS	l.root-servers.net (2001:500:9f::42)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
5	a1-245.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2: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
6	a11-64.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2: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
7	a20-65.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2: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	a.gtld-servers.net (2001:503:a83e::2: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	a.gtld-servers.net (2001:503:a83e::2: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	a.gtld-servers.net (2001:503:a83e::2: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	Value	∑ Queries
www.odenfull.co			1
odenfull.co	0	no CAA entry found	1
co	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
odenfull.co	ok	1
www.odenfull.co		1
_acme-challenge.odenfull.co	Name Error - The domain name does not exist	1
_acme-challenge.www.odenfull.co	Name Error - The domain name does not exist	1
_acme-challenge.odenfull.co.odenfull.co	Name Error - The domain name does not exist	1
_acme-challenge.www.odenfull.co.odenfull.co	Name Error - The domain name does not exist	1
_acme-challenge.www.odenfull.co.www.odenfull.co	Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Value	Status	Description
_dmarc	TXT	_dmarc.odenfull.co	v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;	ok
	TXT	odenfull.co._report._dmarc.onsecureserver.net	mailto:dmarc_rua@onsecureserver.net	ok	Mail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.
	TXT	odenfull.co._report._dmarc.onsecureserver.net	v=DMARC1	ok	Confirmed. Sending reports to external domain is allowed.

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=626543b3-99b7-4e2c-9c99-2640cc2a423b

Last Result: https://check-your-website.server-daten.de/?q=odenfull.co%3A2086 - 2025-11-13 20:58:39

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

<a href="https://check-your-website.server-daten.de/?q=odenfull.co%3A2086" target="_blank">Check this Site: odenfull.co%3A2086</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=odenfull.co:2086