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

...

skip EDNS-Check

skip Content-Check

check links

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
06.06.2024 21:33:32

Older results

U - 30.04.2024 13:54:16

O - 11.03.2024 20:49:52

O - 09.12.2022 10:23:27

O - 01.12.2022 04:38:35

E - 01.10.2021 12:29:09

E - 06.08.2021 10:54:14

H - 21.09.2020 15:27:23

S - 20.07.2019 10:18:27

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
npi.pe		Name Error	yes	1	0
www.npi.pe		Name Error	yes	1	0

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 5613, 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: 21.06.2024, 00:00:00 +, Signature-Inception: 31.05.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: pe
pe	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 7981, DigestType 2 and Digest fEsSwNkWaUcYExx7dgdWE5P7huKjFZznp06p4pr7JvM=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner pe., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.06.2024, 17:00:00 +, Signature-Inception: 06.06.2024, 16:00:00 +, KeyTag 5613, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 37239, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner pe., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 7981, Signer-Name: pe


	RRSIG-Owner pe., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 37239, Signer-Name: pe


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


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


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

Zone: npi.pe
npi.pe	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 "p6nq95s9ne4bpmfhpepnfuthg7r1thfi" between the hashed NSEC3-owner "or6rkeefqrup1g4h4aicj6bi1sfdqalf" and the hashed NextOwner "p7f3vbrj92i48rkr0deeal1r19461fsn". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner or6rkeefqrup1g4h4aicj6bi1sfdqalf.pe., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 37239, Signer-Name: pe


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tok7drblk0d4jm90prqnb1favc8mtb4j" as Owner. That's the Hash of "pe" with the NextHashedOwnerName "tq9vcab7gs815obsqc19jahuitb1i6qh". So that domain name is the Closest Encloser of "npi.pe". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tok7drblk0d4jm90prqnb1favc8mtb4j.pe., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 37239, Signer-Name: pe


	The ClosestEncloser says, that "*.pe" with the Hash "lnhh9v3pls14r0bsrllq80g4p77ci9q8" 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 "lk77876csqk1b8fedm1qu4bhib5hhmjn" and the Next Owner "m5f0dgpro4kcj5e4n3v7qemlo6cncafj", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner lk77876csqk1b8fedm1qu4bhib5hhmjn.pe., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 37239, Signer-Name: pe

Zone: www.npi.pe
www.npi.pe	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tok7drblk0d4jm90prqnb1favc8mtb4j" as Owner. That's the Hash of "pe" with the NextHashedOwnerName "tq9vcab7gs815obsqc19jahuitb1i6qh". So that domain name is the Closest Encloser of "www.npi.pe". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tok7drblk0d4jm90prqnb1favc8mtb4j.pe., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 37239, Signer-Name: pe


	The ClosestEncloser says, that "*.pe" with the Hash "lnhh9v3pls14r0bsrllq80g4p77ci9q8" 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 "lk77876csqk1b8fedm1qu4bhib5hhmjn" and the Next Owner "m5f0dgpro4kcj5e4n3v7qemlo6cncafj", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner lk77876csqk1b8fedm1qu4bhib5hhmjn.pe., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 06.07.2024, 17:50:15 +, Signature-Inception: 06.06.2024, 17:50:15 +, KeyTag 37239, Signer-Name: pe

3. Name Servers

Domain	Nameserver
www.npi.pe	• quipu.rcp.net.pe
npi.pe	• quipu.rcp.net.pe
pe	• a.lactld.org / a5-mvd	•
	• pch.rcp.pe / 3.ams.pch	•
	• pe1.dnsnode.net / s2.amx	•
	X quipu.rcp.net.pe

4. SOA-Entries

Domain:	pe
Zone-Name:	pe
Primary:	quipu.rcp.net.pe
Mail:	operador.rcp.pe
Serial:	2024060613
Refresh:	1800
Retry:	300
Expire:	604800
TTL:	1800
num Entries:	4

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

Domain:	www.npi.pe
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 "npi.pe" is domain, public suffix is ".pe", top-level-domain is ".pe", top-level-domain-type is "country-code", Country is Peru, tld-manager is "Red Cientifica Peruana", num .pe-domains preloaded: 142 (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.
X	Fatal error: Nameserver doesn't support TCP connection: quipu.rcp.net.pe: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
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.npi.pe
	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
A
A	Info:: 4 different Name Servers found: a.lactld.org, pch.rcp.pe, pe1.dnsnode.net, quipu.rcp.net.pe, 4 Name Servers included in Delegation: a.lactld.org, pch.rcp.pe, pe1.dnsnode.net, quipu.rcp.net.pe, 4 Name Servers included in 1 Zone definitions: A.LACTLD.ORG, PCH.RCP.pe, PE1.DNSNODE.NET, QUIPU.RCP.NET.pe, 1 Name Servers listed in SOA.Primary: quipu.rcp.net.pe.
A	Good: Only one SOA.Primary Name Server found.: quipu.rcp.net.pe.
A	Good: SOA.Primary Name Server included in the delegation set.: quipu.rcp.net.pe.
A	Good: All Name Server Domain Names have a Public Suffix.
A
X	Nameserver Timeout checking Echo Capitalization: quipu.rcp.net.pe
X	Nameserver Timeout checking EDNS512: quipu.rcp.net.pe
	Nameserver doesn't pass all EDNS-Checks: quipu.rcp.net.pe: 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: quipu.rcp.net.pe: 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: quipu.rcp.net.pe: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. 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
	Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 154746 milliseconds, 154.746 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	3
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	0	3
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US				0	0	2
CN=E1, O=Let's Encrypt, C=US				0	0	2

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
6945755482 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-03-16 13:57:17	2024-06-14 13:57:16	npi.pe - 1 entries
6821834709 leaf cert	CN=E1, O=Let's Encrypt, C=US	2024-02-26 01:57:35	2024-05-26 01:57:34	*.npi.pe, npi.pe - 2 entries
6813787116 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-02-24 16:15:23	2024-05-24 16:15:22	*.npi.pe, npi.pe - 2 entries
6572694623 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-16 14:09:29	2024-04-15 14:09:28	npi.pe - 1 entries
6457409980 leaf cert	CN=E1, O=Let's Encrypt, C=US	2023-12-28 22:43:51	2024-03-27 22:43:50	*.npi.pe, npi.pe - 2 entries
6402043384 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-12-20 09:47:29	2024-03-19 09:47:28	*.npi.pe, npi.pe - 2 entries
5188564033 precert	CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US	2023-05-06 00:00:00	2024-05-04 23:59:59	*.npi.pe, npi.pe, sni.cloudflaressl.com - 3 entries
4524627631 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-12-08 15:16:03	2023-03-08 15:16:02	npi.pe - 1 entries
4492970960 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2022-12-01 08:47:24	2023-03-01 08:47:23	*.npi.pe, npi.pe - 2 entries
3812599949 precert	CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US	2022-06-06 00:00:00	2023-06-05 23:59:59	*.npi.pe, npi.pe, sni.cloudflaressl.com - 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	4
CN=E1, O=Let's Encrypt, C=US				0	0	3
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	0	3
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12404460795 precert	CN=R3, O=Let's Encrypt, C=US	2024-03-16 12:57:17	2024-06-14 11:57:16	npi.pe 1 entries
12191424699 precert	CN=E1, O=Let's Encrypt, C=US	2024-02-26 00:57:35	2024-05-25 23:57:34	*.npi.pe, npi.pe 2 entries
12178044257 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-02-24 15:15:23	2024-05-24 14:15:22	*.npi.pe, npi.pe 2 entries
11766246889 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-16 13:09:29	2024-04-15 12:09:28	npi.pe 1 entries
11609818524 leaf cert	CN=E1, O=Let's Encrypt, C=US	2023-12-28 21:43:51	2024-03-27 21:43:50	*.npi.pe, npi.pe 2 entries
11509368781 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-12-20 08:47:29	2024-03-19 08:47:28	*.npi.pe, npi.pe 2 entries
11128714842 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-11-17 14:00:26	2024-02-15 14:00:25	npi.pe 1 entries
10949326957 precert	CN=E1, O=Let's Encrypt, C=US	2023-10-30 20:26:41	2024-01-28 20:26:40	*.npi.pe, npi.pe 2 entries
10825428065 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-10-18 17:45:47	2024-01-16 18:45:46	*.npi.pe, npi.pe 2 entries
10751498141 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-09-29 13:04:36	2023-12-28 14:04:35	npi.pe 1 entries
9323331953 precert	CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US	2023-05-05 22:00:00	2024-05-04 21:59:59	*.npi.pe, npi.pe, sni.cloudflaressl.com 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/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

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

No NameServer - IP address - Informations found

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
pe	0		no CAA entry found	1	0

15. TXT - Entries

No TXT entries found

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=d9aa284b-e411-4f6a-89de-1a25b21a839c

Last Result: https://check-your-website.server-daten.de/?q=npi.pe - 2024-06-06 21:33:32

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

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