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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
23.02.2021 12:05:48


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
losnbinossecomenelfuturo.org

Name Error
yes
1
0
www.losnbinossecomenelfuturo.org

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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.03.2021, 05:00:00 +, Signature-Inception: 23.02.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 27558, Flags 256



Public Key with Algorithm 8, KeyTag 34266, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.03.2021, 15:29:59 +, Signature-Inception: 17.02.2021, 14:29:59 +, KeyTag 26974, Signer-Name: org



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest "T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: losnbinossecomenelfuturo.org
losnbinossecomenelfuturo.org
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 "jeriuvehlanb2ijv75so6higu3dit686" between the hashed NSEC3-owner "jerigu044ki52s2fuhbo700tlirvqten" and the hashed NextOwner "jernreqp5g654pa8ihpkh955bko83n44". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner jerigu044ki52s2fuhbo700tlirvqten.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 10.03.2021, 15:29:59 +, Signature-Inception: 17.02.2021, 14:29:59 +, KeyTag 34266, Signer-Name: org



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "d6n22mffurrkkhup4jscmntse266m0lq" as Owner. That's the Hash of "org" with the NextHashedOwnerName "d6n6gr81bv9d3ce1vsg6fn5bau7ub671". So that domain name is the Closest Encloser of "losnbinossecomenelfuturo.org". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner d6n22mffurrkkhup4jscmntse266m0lq.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.03.2021, 11:05:30 +, Signature-Inception: 23.02.2021, 10:05:30 +, KeyTag 34266, Signer-Name: org



The ClosestEncloser says, that "*.org" with the Hash "nrkvoje3pqhcjsfelcggagr5kiqbrapr" 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 "nrkvn0ljdqacnn3kc5q1aek73ra7cldm" and the Next Owner "nrl0iog55fq05ccjgbr9eq8o8afiopec", 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 nrkvn0ljdqacnn3kc5q1aek73ra7cldm.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 10.03.2021, 15:29:59 +, Signature-Inception: 17.02.2021, 14:29:59 +, KeyTag 34266, Signer-Name: org

Zone: www.losnbinossecomenelfuturo.org
www.losnbinossecomenelfuturo.org
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "d6n22mffurrkkhup4jscmntse266m0lq" as Owner. That's the Hash of "org" with the NextHashedOwnerName "d6n6gr81bv9d3ce1vsg6fn5bau7ub671". So that domain name is the Closest Encloser of "www.losnbinossecomenelfuturo.org". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner d6n22mffurrkkhup4jscmntse266m0lq.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.03.2021, 11:05:30 +, Signature-Inception: 23.02.2021, 10:05:30 +, KeyTag 34266, Signer-Name: org



The ClosestEncloser says, that "*.org" with the Hash "nrkvoje3pqhcjsfelcggagr5kiqbrapr" 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 "nrkvn0ljdqacnn3kc5q1aek73ra7cldm" and the Next Owner "nrl0iog55fq05ccjgbr9eq8o8afiopec", 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 nrkvn0ljdqacnn3kc5q1aek73ra7cldm.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 10.03.2021, 15:29:59 +, Signature-Inception: 17.02.2021, 14:29:59 +, KeyTag 34266, Signer-Name: org


3. Name Servers

DomainNameserverNS-IP
www.losnbinossecomenelfuturo.org
  a0.org.afilias-nst.info

losnbinossecomenelfuturo.org
  a0.org.afilias-nst.info

org
  a0.org.afilias-nst.info / ns000b.app27.ams2.afilias-nst.info


  a2.org.afilias-nst.info / FRA3


  b0.org.afilias-nst.org / ns000b.app18.ams2.afilias-nst.info


  b2.org.afilias-nst.org / FRA4


  c0.org.afilias-nst.info / app1.iad1.hosts.meta.redstone.afilias-nst.info-2020121101


  d0.org.afilias-nst.org / ns000a.app32.ams2.afilias-nst.info


4. SOA-Entries


Domain:org
Zone-Name:org
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2014263906
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


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


Domain:www.losnbinossecomenelfuturo.org
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

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "losnbinossecomenelfuturo.org" is domain, public suffix is ".org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 5035 (complete: 142558)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "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.

2. DNS- and NameServer - Checks

A
A
AInfo:: 6 different Name Servers found: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org, 6 Name Servers included in Delegation: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org, 6 Name Servers included in 1 Zone definitions: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org, 1 Name Servers listed in SOA.Primary: a0.org.afilias-nst.info.
AGood: Only one SOA.Primary Name Server found.: a0.org.afilias-nst.info.
AGood: SOA.Primary Name Server included in the delegation set.: a0.org.afilias-nst.info.
AGood: All Name Server Domain Names have a Public Suffix.
A
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a0.org.afilias-nst.info: 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: a0.org.afilias-nst.info: 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: a0.org.afilias-nst.info: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns000b.app27.ams2.afilias-nst.info). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: b2.org.afilias-nst.org: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (FRA4). COOKIE: ok. 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.

3. 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.
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: 26570 milliseconds, 26.570 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" > 2019 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. 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
org
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c1d2397c-feb4-439c-ac53-1d6c01c59ef2


Last Result: https://check-your-website.server-daten.de/?q=losnbinossecomenelfuturo.org - 2021-02-23 12:05:48


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

<a href="https://check-your-website.server-daten.de/?q=losnbinossecomenelfuturo.org" target="_blank">Check this Site: losnbinossecomenelfuturo.org</a>