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




X

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

Checked:
18.03.2023 10:14:23


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
redpolitica.mx

Refused
yes
1
0
www.redpolitica.mx

Refused
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 951, 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: 02.04.2023, 00:00:00 +, Signature-Inception: 12.03.2023, 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 61885, DigestType 2 and Digest vTTcetddlBJYEDN3AMbQ+e5dv9TVLRPC2IrF5w3rj3k=



1 RRSIG RR to validate DS RR found



RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.03.2023, 05:00:00 +, Signature-Inception: 18.03.2023, 04:00:00 +, KeyTag 951, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20260, Flags 256



Public Key with Algorithm 8, KeyTag 61885, 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: 16.04.2023, 00:00:00 +, Signature-Inception: 17.03.2023, 00:00:00 +, KeyTag 20260, Signer-Name: mx



RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.05.2023, 14:00:00 +, Signature-Inception: 02.03.2023, 15:00:00 +, KeyTag 61885, Signer-Name: mx



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



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



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

Zone: redpolitica.mx
redpolitica.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 "i37ffbvvd8l354q4v5opu6qtm2mt2juo" between the hashed NSEC3-owner "i3707rebn5qcrhet67pa0oe56ldcrsgh" and the hashed NextOwner "i37mt33ug4ihevouis05anp6u376bpka". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner i3707rebn5qcrhet67pa0oe56ldcrsgh.mx., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 16.04.2023, 00:00:00 +, Signature-Inception: 17.03.2023, 00:00:00 +, KeyTag 20260, Signer-Name: mx



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "jfb0tscd628iasoj33kgfq8cvuet0gon" as Owner. That's the Hash of "mx" with the NextHashedOwnerName "jfctqq47smpleau5ekfsoi7u14kj82fq". So that domain name is the Closest Encloser of "redpolitica.mx". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner jfb0tscd628iasoj33kgfq8cvuet0gon.mx., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 16.04.2023, 00:00:00 +, Signature-Inception: 17.03.2023, 00:00:00 +, KeyTag 20260, Signer-Name: mx



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
redpolitica.mx
  ns1035.banahosting.com / single-1035.banahosting.com
66.225.201.3
Chicago/Illinois/United States (US) - Server Central Network


  ns1036.banahosting.com / single-1035.banahosting.com
66.225.201.4
Chicago/Illinois/United States (US) - Server Central Network

mx
  c.mx-ns.mx


  e.mx-ns.mx / 2.ber.pch


  i.mx-ns.mx / TLD_Host2.Amsterdam_Node1


  m.mx-ns.mx


  o.mx-ns.mx


  x.mx-ns.mx / TLD_Host2.Amsterdam_Node1


4. SOA-Entries


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


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


Domain:redpolitica.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

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "redpolitica.mx" is domain, public suffix is ".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: 337 (complete: 220007)
AGood: 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.
XFatal error: Nameserver doesn't support TCP connection: ns1035.banahosting.com / 66.225.201.3: Refused
XFatal error: Nameserver doesn't support TCP connection: ns1036.banahosting.com / 66.225.201.4: Refused
BNo _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.redpolitica.mx

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

A
A
AInfo:: 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.
AGood: Only one SOA.Primary Name Server found.: m.mx-ns.mx.
AGood: SOA.Primary Name Server included in the delegation set.: m.mx-ns.mx.
AGood: All Name Server Domain Names have a Public Suffix.
A
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1035.banahosting.com / 66.225.201.3: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (single-1035.banahosting.com). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1036.banahosting.com / 66.225.201.4: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (single-1035.banahosting.com). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
AGood: 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

AGood: 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
ADuration: 50510 milliseconds, 50.510 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)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
1
1
CN=E1, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4869772884
leaf cert
CN=E1, O=Let's Encrypt, C=US
2023-02-25 04:02:36
2023-05-26 04:02:35
*.redpolitica.mx, redpolitica.mx - 2 entries


4869730251
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-02-25 03:46:11
2023-05-26 03:46:10
redpolitica.mx - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
1
1
CN=E1, O=Let's Encrypt, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
8806206493
leaf cert
CN=E1, O=Let's Encrypt, C=US
2023-02-25 03:02:36
2023-05-26 02:02:35
*.redpolitica.mx, redpolitica.mx
2 entries


8806127425
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-02-25 02:46:11
2023-05-26 01:46:10
redpolitica.mx
1 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:


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
redpolitica.mx
-5

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
mx
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
redpolitica.mx

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
_acme-challenge.redpolitica.mx

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
_acme-challenge.redpolitica.mx.redpolitica.mx

Refused - The name server refuses to perform the specified operation for policy reasons
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

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=c83fd4d4-3625-4344-b7dc-5930710c2e85


Last Result: https://check-your-website.server-daten.de/?q=redpolitica.mx - 2023-03-18 10:14:23


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

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