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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
15.04.2025 00:35:33

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
corporate.renova2.net	A	189.131.127.150 Álvaro Obregón/Mexico City/Mexico (MX) - UNINET Hostname: dsl-189-131-127-150-dyn.prod-infinitum.com.mx	yes	1	0
	AAAA		yes
www.corporate.renova2.net		Name Error	yes	1	0
*.renova2.net	A	189.131.43.242	yes
	AAAA		yes
	CNAME		yes
*.corporate.renova2.net	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: 02.05.2025, 00:00:00 +, Signature-Inception: 11.04.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: net
net	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.04.2025, 17:00:00 +, Signature-Inception: 14.04.2025, 16: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


	3 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 10024, Flags 256


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


	Public Key with Algorithm 13, KeyTag 45412, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.04.2025, 14:10:35 +, Signature-Inception: 12.04.2025, 14:05:35 +, KeyTag 37331, Signer-Name: net


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: renova2.net
renova2.net	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 "24kaukic24tdaom8b92ofpjhncdinfef" between the hashed NSEC3-owner "24kafs38gjngo0vu9o0lhaua9517ed10" and the hashed NextOwner "24kd676l54jmdnvhg2avrvaunleroclq". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 24kafs38gjngo0vu9o0lhaua9517ed10.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 21.04.2025, 03:04:03 +, Signature-Inception: 14.04.2025, 01:54:03 +, KeyTag 10024, Signer-Name: net


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "renova2.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 21.04.2025, 03:05:52 +, Signature-Inception: 14.04.2025, 01:55:52 +, KeyTag 10024, Signer-Name: net


	0 DNSKEY RR found




Zone: corporate.renova2.net
corporate.renova2.net	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.corporate.renova2.net
www.corporate.renova2.net	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.corporate.renova2.net	• ns2.no-ip.com
corporate.renova2.net	• ns2.no-ip.com / frana2	194.62.180.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:180::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
renova2.net	• ns1.no-ip.com / frana1	194.62.181.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1810::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• ns2.no-ip.com / frana2	194.62.180.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:180::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• ns3.no-ip.com / frana1	204.16.255.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:2550::53 Amsterdam/North Holland/The Netherlands (NL) - Vitalwerks Internet Solutions, LLC	•
	• ns4.no-ip.com / frana2	204.16.254.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2620:0:2e64::53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• ns5.no-ip.com / frana1	194.62.181.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
net	• 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:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1744670115
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	13

Domain:	renova2.net
Zone-Name:	renova2.net
Primary:	ns2.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2024060651
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	9

Domain:	corporate.renova2.net
Zone-Name:	renova2.net
Primary:	ns2.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2024060651
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	2

Domain:	www.corporate.renova2.net
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

Domainname	Http-Status	Sec.	G
• http://corporate.renova2.net/ 189.131.127.150	-110	1.687	W
ResponseEnded (10, 0x80131620). An error occurred while sending the request.

• https://corporate.renova2.net/ 189.131.127.150	-110	2.820	W
ResponseEnded (10, 0x80131620). An error occurred while sending the request.

• http://corporate.renova2.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 189.131.127.150	-110	1.704	W
ResponseEnded (10, 0x80131620). An error occurred while sending the request.
Visible Content:

• https://189.131.127.150/ 189.131.127.150	-110	2.524	W
ResponseEnded (10, 0x80131620). An error occurred while sending the request.

7. Comments

	1. General Results, most used to calculate the result
A	name "corporate.renova2.net" is subdomain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 10340 (complete: 270180)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: corporate.renova2.net 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: corporate.renova2.net has no ipv6 address.
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
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	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 corporate.renova2.net, 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.corporate.renova2.net
	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:: 5 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
A	Info:: 5 Queries complete, 5 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.no-ip.com (194.62.181.53, 2a07:dc00:1810::53), ns1.no-ip.com (194.62.181.53, 2a07:dc00:1810::53), ns2.no-ip.com (194.62.180.53, 2a07:dc00:180::53), ns3.no-ip.com (204.16.255.53, 2a07:dc00:2550::53), ns4.no-ip.com (204.16.254.53, 2620:0:2e64::53)
A	Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 5 different Name Servers found: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com, 4 Name Servers included in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, 5 Name Servers included in 1 Zone definitions: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com, 1 Name Servers listed in SOA.Primary: ns2.no-ip.com.
A	Good: Only one SOA.Primary Name Server found.: ns2.no-ip.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns2.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.no-ip.com (194.62.181.53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.no-ip.com (2a07:dc00:1810::53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.no-ip.com (194.62.180.53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.no-ip.com (2a07:dc00:180::53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.no-ip.com (204.16.255.53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.no-ip.com (2a07:dc00:2550::53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4.no-ip.com (204.16.254.53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4.no-ip.com (2620:0:2e64::53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.com.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns5.no-ip.com (194.62.181.53): Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Zone, missing in Delegation: ns5.no-ip.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: 5 different Name Servers found
A	Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (1 Name Servers without IPv6)
	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.: 5 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: no-ip.com
A	Good: Name servers with different Country locations found: 5 Name Servers, 2 Countries: NL, US
A	Info: Ipv4-Subnet-list: 5 Name Servers, 2 different subnets (first Byte): 194., 204., 2 different subnets (first two Bytes): 194.62., 204.16., 4 different subnets (first three Bytes): 194.62.180., 194.62.181., 204.16.254., 204.16.255.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2620:, 2a07:, 2 different subnets (first two blocks): 2620:0000:, 2a07:dc00:, 4 different subnets (first three blocks): 2620:0000:2e64:, 2a07:dc00:0180:, 2a07:dc00:1810:, 2a07:dc00:2550:, 4 different subnets (first four blocks): 2620:0000:2e64:0000:, 2a07:dc00:0180:0000:, 2a07:dc00:1810:0000:, 2a07:dc00:2550:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns2.no-ip.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
	http://corporate.renova2.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 189.131.127.150	-110	Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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: 75357 milliseconds, 75.357 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=E5, O=Let's Encrypt, C=US				0	7	7
CN=E6, O=Let's Encrypt, C=US				0	3	3

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10105955713 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-04-14 12:31:04	2025-07-13 12:31:03	corporate.renova2.net - 1 entries
10078336105 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-04-11 20:11:28	2025-07-10 20:11:27	corporate.renova2.net - 1 entries
10043103237 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-04-08 16:44:11	2025-07-07 16:44:10	corporate.renova2.net - 1 entries
10042819031 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-04-08 16:01:39	2025-07-07 16:01:38	corporate.renova2.net - 1 entries
10042351274 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-04-08 14:55:27	2025-07-07 14:55:26	corporate.renova2.net - 1 entries
10041479029 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-04-08 13:00:54	2025-07-07 13:00:53	corporate.renova2.net - 1 entries
10041248389 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-04-08 12:31:41	2025-07-07 12:31:40	corporate.renova2.net - 1 entries
9884040409 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-03-23 14:23:51	2025-06-21 14:23:50	corporate.renova2.net - 1 entries
9868157806 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-03-21 22:19:12	2025-06-19 22:19:11	corporate.renova2.net - 1 entries
9848594106 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-03-19 22:00:22	2025-06-17 22:00:21	corporate.renova2.net - 1 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=E5, O=Let's Encrypt, C=US				0	7	7
CN=E6, O=Let's Encrypt, C=US				0	3	3

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
17843162852 precert	CN=E5, O=Let's Encrypt, C=US	2025-04-14 10:31:04	2025-07-13 10:31:03	corporate.renova2.net 1 entries
17797532601 precert	CN=E5, O=Let's Encrypt, C=US	2025-04-11 18:11:28	2025-07-10 18:11:27	corporate.renova2.net 1 entries
17724380568 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-04-08 14:44:11	2025-07-07 14:44:10	corporate.renova2.net 1 entries
17723625827 precert	CN=E6, O=Let's Encrypt, C=US	2025-04-08 14:01:39	2025-07-07 14:01:38	corporate.renova2.net 1 entries
17723308281 precert	CN=E6, O=Let's Encrypt, C=US	2025-04-08 12:55:27	2025-07-07 12:55:26	corporate.renova2.net 1 entries
17720145528 precert	CN=E5, O=Let's Encrypt, C=US	2025-04-08 11:00:54	2025-07-07 11:00:53	corporate.renova2.net 1 entries
17733552634 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-04-08 10:31:41	2025-07-07 10:31:40	corporate.renova2.net 1 entries
17345069351 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-03-23 13:23:51	2025-06-21 12:23:50	corporate.renova2.net 1 entries
17302907215 precert	CN=E5, O=Let's Encrypt, C=US	2025-03-21 21:19:12	2025-06-19 20:19:11	corporate.renova2.net 1 entries
17260109086 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-03-19 21:00:22	2025-06-17 20:00:21	corporate.renova2.net 1 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: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.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	ns1.no-ip.com: 194.62.181.53, 2a07:dc00:1810::53	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
3	ns5.no-ip.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
4	ns5.no-ip.com: 194.62.181.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
5	ns5.no-ip.com: No AAAA record found	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)

14. CAA - Entries

Domainname	Value	∑ Queries
corporate.renova2.net	no CAA entry found	1
renova2.net	no CAA entry found	1
net	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
renova2.net	202311301134531za8pbd7i7sd93m4ymcep5ccxic68egvg206nlwzjqsi64yan1	ok	1
renova2.net	forward-email=antonior.imprasc@gmail.com	ok	1
renova2.net	trustcor-ca-+3qkkPH9BViBALYrNDiJOcwTotG2DLUbqBVYgZbWPTKNHT/Ec9hD53jR/Q7K3YPKlgw2sVZf7Xld4Vvt/+JqvbX5QpX4aRmO6gfWMj5gv/hP4TMLfWZVtATbKgC6+Q8bkRUuGp/LjkKzsI8bldMV	ok	1
corporate.renova2.net		ok	1
_acme-challenge.corporate.renova2.net		Name Error - The domain name does not exist	1
_acme-challenge.corporate.renova2.net.renova2.net		perhaps wrong	1
_acme-challenge.corporate.renova2.net.corporate.renova2.net		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

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=cc8a376d-8740-4697-8c93-30c97af96716

Last Result: https://check-your-website.server-daten.de/?q=corporate.renova2.net - 2025-04-15 00:35:33

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

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