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:
29.11.2024 23:17:54

Older results

X - 27.11.2024 21:52:33

1. IP-Addresses

Host	Type	is auth.	∑ Queries	∑ Timeout
ircep.gob.mx		yes	2	0
www.ircep.gob.mx		yes	2	0
*.ircep.gob.mx	A	yes
	AAAA	yes
	CNAME	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 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 61050, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 62752, DigestType 2 and Digest Gy9V2/bPuetmsJY9qmu+LLvcuFFZj+wl7CzNyaN4WhI=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2024, 17:00:00 +, Signature-Inception: 29.11.2024, 16:00:00 +, KeyTag 61050, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 42025, Flags 256


	Public Key with Algorithm 8, KeyTag 55120, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2024, 00:00:00 +, Signature-Inception: 29.11.2024, 00:00:00 +, KeyTag 42025, Signer-Name: mx


	RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.01.2025, 15:00:00 +, Signature-Inception: 29.11.2024, 15:00:00 +, KeyTag 62752, Signer-Name: mx


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


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


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

Zone: gob.mx
gob.mx	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 62752, DigestType 2 and Digest 2SB5WhjH7isaHtPL4vyNvK7LQGF0EWP3y4HDYpyTXdM=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner gob.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2024, 00:00:00 +, Signature-Inception: 29.11.2024, 00:00:00 +, KeyTag 42025, Signer-Name: mx


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 42025, Flags 256


	Public Key with Algorithm 8, KeyTag 55120, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gob.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2024, 00:00:00 +, Signature-Inception: 29.11.2024, 00:00:00 +, KeyTag 42025, Signer-Name: gob.mx


	RRSIG-Owner gob.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.01.2025, 15:00:00 +, Signature-Inception: 29.11.2024, 15:00:00 +, KeyTag 62752, Signer-Name: gob.mx


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


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


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

Zone: ircep.gob.mx
ircep.gob.mx	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 "qhcrpt5qnfpsdc10u183dfr92s2phd58" between the hashed NSEC3-owner "qfnjlb9f2u0j9jabi4vrk4ancouvjbi7" and the hashed NextOwner "qkkc1gcp6i67v3gcin9c4c9dupvs0p3c". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner qfnjlb9f2u0j9jabi4vrk4ancouvjbi7.gob.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 29.12.2024, 00:00:00 +, Signature-Inception: 29.11.2024, 00:00:00 +, KeyTag 42025, Signer-Name: gob.mx


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "psl8avpcbqr0reotpljindr4pb48egc9" as Owner. That's the Hash of "gob.mx" with the NextHashedOwnerName "ptg61ghq08in50flroquho15a9t7jrnd". So that domain name is the Closest Encloser of "ircep.gob.mx". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner psl8avpcbqr0reotpljindr4pb48egc9.gob.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 29.12.2024, 00:00:00 +, Signature-Inception: 29.11.2024, 00:00:00 +, KeyTag 42025, Signer-Name: gob.mx


	0 DNSKEY RR found




Zone: www.ircep.gob.mx
www.ircep.gob.mx	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
ircep.gob.mx	• ns1.ircep.gob.mx
	• ns2.ircep.gob.mx
gob.mx	• c.mx-ns.mx	192.100.224.1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	•	2001:1258::1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	• e.mx-ns.mx / 2.ams.pch	189.201.244.1 Montreal/Quebec/Canada (CA) - WoodyNet, Inc.	•
	•	2801:c4:c0::1 Monterrey/Nuevo León/Mexico (MX) - WoodyNet, Inc.	•
	• i.mx-ns.mx	207.248.68.1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	•	2801:c4:d0::1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	• m.mx-ns.mx	200.94.176.1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	•	2001:13c7:7000::1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	• o.mx-ns.mx	200.23.1.1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	•	2001:1201::1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
	• x.mx-ns.mx / TLD_Host1.Frankfurt_Node1	201.131.252.1 Monterrey/Nuevo León/Mexico (MX) - NeuStar, Inc.	•
	•	2001:1201:10::1 Monterrey/Nuevo León/Mexico (MX) - Network Information Center México	•
mx	• c.mx-ns.mx		•
	• e.mx-ns.mx / 6.ams.pch		•
	• i.mx-ns.mx		•
	• m.mx-ns.mx		•
	• o.mx-ns.mx		•
	• x.mx-ns.mx / TLD_Host1.Frankfurt_Node1		•

4. SOA-Entries

Domain:	mx
Zone-Name:	mx
Primary:	m.mx-ns.mx
Mail:	hostmaster.nic.mx
Serial:	1732918557
Refresh:	900
Retry:	900
Expire:	604800
TTL:	1800
num Entries:	6

Domain:	gob.mx
Zone-Name:	gob.mx
Primary:	m.mx-ns.mx
Mail:	hostmaster.nic.mx
Serial:	1732913161
Refresh:	900
Retry:	900
Expire:	604800
TTL:	1800
num Entries:	12

Domain:	ircep.gob.mx
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	2

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 "ircep.gob.mx" is domain, public suffix is ".gob.mx", top-level-domain is ".mx", top-level-domain-type is "country-code", Country is Mexico, tld-manager is "NIC-Mexico ITESM - Campus Monterrey", num .mx-domains preloaded: 414 (complete: 263653)
A	Good: No asked Authoritative Name Server had a timeout
	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.ircep.gob.mx
	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:: 1 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
A	Info:: 1 Queries complete, 1 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Info:: 6 different Name Servers found: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, 6 Name Servers included in Delegation: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, 6 Name Servers included in 1 Zone definitions: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, 1 Name Servers listed in SOA.Primary: m.mx-ns.mx.
A	Good: Only one SOA.Primary Name Server found.: m.mx-ns.mx.
A	Good: SOA.Primary Name Server included in the delegation set.: m.mx-ns.mx.
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	Info: Ipv4-Subnet-list: 6 Name Servers, 5 different subnets (first Byte): 189., 192., 200., 201., 207., 6 different subnets (first two Bytes): 189.201., 192.100., 200.23., 200.94., 201.131., 207.248., 6 different subnets (first three Bytes): 189.201.244., 192.100.224., 200.23.1., 200.94.176., 201.131.252., 207.248.68.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2801:, 4 different subnets (first two blocks): 2001:1201:, 2001:1258:, 2001:13c7:, 2801:00c4:, 6 different subnets (first three blocks): 2001:1201:0000:, 2001:1201:0010:, 2001:1258:0000:, 2001:13c7:7000:, 2801:00c4:00c0:, 2801:00c4:00d0:, 6 different subnets (first four blocks): 2001:1201:0000:0000:, 2001:1201:0010:0000:, 2001:1258:0000:0000:, 2001:13c7:7000:0000:, 2801:00c4:00c0:0000:, 2801:00c4:00d0:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 12 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 12 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns1.ircep.gob.mx: 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: ns2.ircep.gob.mx: 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: 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: 245676 milliseconds, 245.676 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)

No CertSpotter - CT-Log entries found

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

No CRT - CT-Log entries found

11. Html-Content - Entries

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

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

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: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx

QNr.	Domain	Type	NS used
1	mx	NS	k.root-servers.net (2001:7fd::1)
	Answer: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx

14. CAA - Entries

Domainname	flag	Value	∑ Queries
ircep.gob.mx			2
gob.mx	0	no CAA entry found	1
mx	0	no CAA entry found	1

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=f27efdf3-e0b0-4bdf-b78c-36969e85c162

Last Result: https://check-your-website.server-daten.de/?q=ircep.gob.mx - 2024-11-29 23:17: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=ircep.gob.mx" target="_blank">Check this Site: ircep.gob.mx</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=ircep.gob.mx