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:
04.09.2024 15:59:54

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
nhentai.net	A		yes	1	0
	AAAA		yes
www.nhentai.net		Name Error	yes	1	0
*.nhentai.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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 20038, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


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


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


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

Zone: 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: 17.09.2024, 05:00:00 +, Signature-Inception: 04.09.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 42924, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.09.2024, 14:10:35 +, Signature-Inception: 25.08.2024, 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: nhentai.net
nhentai.net	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 21697, DigestType 2 and Digest ngnmN5NugMt5ew5sIrI2ddeHssrXUGZxh/wSqA9JSaY=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner nhentai.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 11.09.2024, 11:50:22 +, Signature-Inception: 04.09.2024, 10:40:22 +, KeyTag 42924, Signer-Name: net


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 29829, Flags 256


	Public Key with Algorithm 8, KeyTag 61170, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner nhentai.net., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 21697, Signer-Name: nhentai.net


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


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


	A-Query sends a valid NSEC3 RR as result with the hashed query name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" equal the hashed NSEC3-owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" and the hashed NextOwner "t6qcb7vosjq8jce2n5uqjpnd9htma36b". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" equal the hashed NSEC3-owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" and the hashed NextOwner "t6qcb7vosjq8jce2n5uqjpnd9htma36b". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" equal the hashed NSEC3-owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" and the hashed NextOwner "t6qcb7vosjq8jce2n5uqjpnd9htma36b". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" equal the hashed NSEC3-owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" and the hashed NextOwner "t6qcb7vosjq8jce2n5uqjpnd9htma36b". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.nhentai.net) sends a valid NSEC3 RR as result with the hashed owner name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" (unhashed: nhentai.net). So that's the Closest Encloser of the query name. TLSA-Query (_443._tcp.nhentai.net) sends a valid NSEC3 RR as result with the owner name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" greater the NextOwner-Name "t6qcb7vosjq8jce2n5uqjpnd9htma36b", so the NSEC3 covers the end of the zone. The hashed query name "s2rna72pi90itgbvp5bu28ifovvhjuam" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "t6qcb7vosjq8jce2n5uqjpnd9htma36b" equal the hashed NSEC3-owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" and the hashed NextOwner "t6qcb7vosjq8jce2n5uqjpnd9htma36b". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	Status: Good. NoData-Proof required and found.

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


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "t6qcb7vosjq8jce2n5uqjpnd9htma36b" as Owner. That's the Hash of "nhentai.net" with the NextHashedOwnerName "t6qcb7vosjq8jce2n5uqjpnd9htma36b". So that domain name is the Closest Encloser of "www.nhentai.net". Opt-Out: False. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	The ClosestEncloser says, that "*.nhentai.net" with the Hash "90vufpt350mar82tmva3nha764k7j6ml" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" and the Next Owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner t6qcb7vosjq8jce2n5uqjpnd9htma36b.nhentai.net., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 29829, Signer-Name: nhentai.net


	The NSEC3-Owner "t6qcb7vosjq8jce2n5uqjpnd9htma36b" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.

3. Name Servers

Domain	Nameserver	NS-IP
www.nhentai.net	• ns1.openprovider.nl
nhentai.net	• ns1.openprovider.nl / 67m48	162.159.26.10 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:1a0a San Francisco/California/United States (US) - Cloudflare	•
	• ns2.openprovider.be / 67m67	162.159.27.96 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:1b60 San Francisco/California/United States (US) - Cloudflare	•
	• ns3.openprovider.eu / 67m79	162.159.48.89 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:3059 San Francisco/California/United States (US) - Cloudflare	•
net	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• 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:	1725458594
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	9

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

Domain:	nhentai.net
Zone-Name:	nhentai.net
Primary:	ns1.openprovider.nl
Mail:	dns.openprovider.eu
Serial:	2024090402
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	3600
num Entries:	6

Domain:	www.nhentai.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	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "nhentai.net" is domain, 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: 9342 (complete: 245733)
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.
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.nhentai.net
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
A	Info:: 12 Queries complete, 12 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 3 different Name Servers found: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu, 3 Name Servers included in Delegation: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu, 3 Name Servers included in 1 Zone definitions: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu, 1 Name Servers listed in SOA.Primary: ns1.openprovider.nl.
A	Good: Only one SOA.Primary Name Server found.: ns1.openprovider.nl.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.openprovider.nl.
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: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu
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: 3 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found
A	Good: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 3 Top Level Domains: nl, eu, be
A	Good: Name Servers with different domain names found.: 3 different Domains found
A	Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: CA, US
A	Info: Ipv4-Subnet-list: 3 Name Servers, 1 different subnets (first Byte): 162., 1 different subnets (first two Bytes): 162.159., 3 different subnets (first three Bytes): 162.159.26., 162.159.27., 162.159.48.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
	Fatal: All Name Server IPv6 addresses from the same subnet.
A	Good: Nameserver supports TCP connections: 6 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 6 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns1.openprovider.nl: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
	Nameserver doesn't pass all EDNS-Checks: ns1.openprovider.nl / 162.159.26.10: 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 (67m48). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.openprovider.be / 162.159.27.96: 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 (67m67). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns3.openprovider.eu / 162.159.48.89: 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 (67m79). COOKIE: ok. CLIENTSUBNET: ok.
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: 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: 271716 milliseconds, 271.716 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=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	2	2
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	1	1
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US				0	1	1
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US				0	1	1
CN=WE1, O=Google Trust Services, C=US				0	1	1
CN=E6, O=Let's Encrypt, C=US				0	1	1
CN=R11, O=Let's Encrypt, C=US				0	1	1
CN=WR1, O=Google Trust Services, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
7700266636 precert	CN=WE1, O=Google Trust Services, C=US	2024-07-13 06:58:57	2024-10-11 06:58:56	*.nhentai.net, nhentai.net - 2 entries
7700265541 precert	CN=WR1, O=Google Trust Services, C=US	2024-07-13 06:58:35	2024-10-11 06:58:34	*.nhentai.net, nhentai.net - 2 entries
7699152854 leaf cert	CN=E6, O=Let's Encrypt, C=US	2024-07-13 03:14:17	2024-10-11 03:14:16	*.nhentai.net, nhentai.net - 2 entries
7699144114 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-07-13 03:13:38	2024-10-11 03:13:37	*.nhentai.net, nhentai.net - 2 entries
6948063325 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-03-17 00:00:00	2025-03-17 23:59:59	*.nhentai.net, nhentai.net - 2 entries
6948221752 leaf cert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-03-17 00:00:00	2025-03-17 23:59:59	*.nhentai.net, nhentai.net - 2 entries
6948870900 precert	CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US	2024-03-17 00:00:00	2024-12-31 23:59:59	*.nhentai.net, nhentai.net - 2 entries
6948870904 leaf cert	CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US	2024-03-17 00:00:00	2024-12-31 23:59:59	*.nhentai.net, nhentai.net - 2 entries
5804800870 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2023-09-05 00:00:00	2024-10-05 23:59:59	*.nhentai.net, nhentai.net - 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=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	2	2
CN=E1, O=Let's Encrypt, C=US				0	0	2
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	0	2
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	2
CN=WE1, O=Google Trust Services, C=US				0	1	1
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	1	1
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US				0	1	1
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US				0	1	1
CN=WR1, O=Google Trust Services, C=US				0	1	1
CN=R11, O=Let's Encrypt, C=US				0	1	1
CN=E6, O=Let's Encrypt, C=US				0	1	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
13719833655 precert	CN=WE1, O=Google Trust Services, C=US	2024-07-13 04:58:57	2024-10-11 04:58:56	*.nhentai.net, nhentai.net 2 entries
13719830849 precert	CN=WR1, O=Google Trust Services, C=US	2024-07-13 04:58:35	2024-10-11 04:58:34	*.nhentai.net, nhentai.net 2 entries
13741499571 leaf cert	CN=E6, O=Let's Encrypt, C=US	2024-07-13 01:14:17	2024-10-11 01:14:16	*.nhentai.net, nhentai.net 2 entries
13741494642 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-07-13 01:13:38	2024-10-11 01:13:37	*.nhentai.net, nhentai.net 2 entries
13078214181 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-05-15 01:40:18	2024-08-13 01:40:17	*.nhentai.net, nhentai.net 2 entries
13080464997 leaf cert	CN=E1, O=Let's Encrypt, C=US	2024-05-15 01:11:11	2024-08-13 01:11:10	*.nhentai.net, nhentai.net 2 entries
13080464901 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-05-15 01:11:09	2024-08-13 01:11:08	*.nhentai.net, nhentai.net 2 entries
13008109735 leaf cert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-03-17 01:16:30	2024-06-15 00:16:29	*.nhentai.net, nhentai.net 2 entries
12410163405 precert	CN=E1, O=Let's Encrypt, C=US	2024-03-17 01:16:03	2024-06-15 00:16:02	*.nhentai.net, nhentai.net 2 entries
12410158242 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-03-17 01:15:55	2024-06-15 00:15:54	*.nhentai.net, nhentai.net 2 entries
12408642689 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-03-16 23:00:00	2025-03-17 22:59:59	*.nhentai.net, nhentai.net 2 entries
12408942927 precert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-03-16 23:00:00	2025-03-17 22:59:59	*.nhentai.net, nhentai.net 2 entries
12410126256 precert	CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US	2024-03-16 23:00:00	2024-12-31 22:59:59	*.nhentai.net, nhentai.net 2 entries
12410148942 leaf cert	CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US	2024-03-16 23:00:00	2024-12-31 22:59:59	*.nhentai.net, nhentai.net 2 entries
10304787153 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2023-09-04 22:00:00	2024-10-05 21:59:59	*.nhentai.net, nhentai.net 2 entries

11. Html-Content - Entries

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

12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu

QNr.	Domain	Type	NS used
1	nl	NS	b.root-servers.net (2001:500:200::b)
	Answer: ns1.dns.nl, ns3.dns.nl, ns4.dns.nl
2	ns1.openprovider.nl	NS	ns1.dns.nl (2001:678:2c:0:194:0:28:53)
	Answer: ns-eu-central-1.openprovider.eu, ns-eu-west-1.openprovider.eu, ns-eu-west-2.openprovider.eu
3	be	NS	e.root-servers.net (2001:500:a8::e)
	Answer: a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be, y.nsset.be, z.nsset.be
4	ns2.openprovider.be	NS	a.nsset.be (2001:678:9::1)
	Answer: ns-eu-central-1.openprovider.eu, ns-eu-west-1.openprovider.eu, ns-eu-west-2.openprovider.eu
5	eu	NS	l.root-servers.net (2001:500:9f::42)
	Answer: be.dns.eu, si.dns.eu, w.dns.eu, x.dns.eu, y.dns.eu
6	ns3.openprovider.eu	NS	si.dns.eu (2001:1470:8000:100::62)
	Answer: ns-eu-central-1.openprovider.eu, ns-eu-west-1.openprovider.eu, ns-eu-west-2.openprovider.eu
	Answer: ns-eu-central-1.openprovider.eu 18.194.228.62, 2a05:d014:f80:6e00:b20f:a574:7f25:31ad
	Answer: ns-eu-west-1.openprovider.eu 2a05:d018:61d:bd00:c886:556d:56a4:db8b, 52.19.66.106
	Answer: ns-eu-west-2.openprovider.eu 2a05:d01c:433:e000:9d6a:209f:a4ad:3c7, 52.56.180.255
7	ns1.openprovider.nl: 162.159.26.10	A	ns-eu-central-1.openprovider.eu (2a05:d014:f80:6e00:b20f:a574:7f25:31ad)
8	ns1.openprovider.nl: 2400:cb00:2049:1::a29f:1a0a	AAAA	ns-eu-central-1.openprovider.eu (2a05:d014:f80:6e00:b20f:a574:7f25:31ad)
9	ns2.openprovider.be: 162.159.27.96	A	ns-eu-central-1.openprovider.eu (2a05:d014:f80:6e00:b20f:a574:7f25:31ad)
10	ns2.openprovider.be: 2400:cb00:2049:1::a29f:1b60	AAAA	ns-eu-central-1.openprovider.eu (2a05:d014:f80:6e00:b20f:a574:7f25:31ad)
11	ns3.openprovider.eu: 162.159.48.89	A	ns-eu-central-1.openprovider.eu (2a05:d014:f80:6e00:b20f:a574:7f25:31ad)
12	ns3.openprovider.eu: 2400:cb00:2049:1::a29f:3059	AAAA	ns-eu-central-1.openprovider.eu (2a05:d014:f80:6e00:b20f:a574:7f25:31ad)

13. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
nhentai.net	0		no CAA entry found	1	0
net	0		no CAA entry found	1	0

14. TXT - Entries

Domainname	Status	∑ Queries
nhentai.net	ok	1
_acme-challenge.nhentai.net	Name Error - The domain name does not exist	1
_acme-challenge.nhentai.net.nhentai.net	Name Error - The domain name does not exist	1

15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06, SMTP-TLS-Reporting is alpa - 2024-07-13)

No DomainServiceEntries entries found

16. Cipher Suites

No Ciphers found

17. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=4c403349-8f54-4fdd-b421-6f94746c076a

Last Result: https://check-your-website.server-daten.de/?q=nhentai.net - 2024-09-04 15:59:54

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

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