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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
17.10.2020 23:29:47


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
certifiedspanish.co

Name Error
yes
1
0
www.certifiedspanish.co

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 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 43834, DigestType 1 and Digest SVfKk+DWAprIv98DmtIumK1yGts=



DS with Algorithm 8, KeyTag 43834, DigestType 2 and Digest poYC7DDE5fXTOmJNNVSaf2osk5OdSyELqPpITzsOCE4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.10.2020, 17:00:00 +, Signature-Inception: 17.10.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 64278, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 518400 sec, Signature-expiration: 11.11.2020, 14:35:54 +, Signature-Inception: 12.10.2020, 13:48:46 +, KeyTag 43834, Signer-Name: co



RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 518400 sec, Signature-expiration: 11.11.2020, 14:35:54 +, Signature-Inception: 12.10.2020, 13:48:46 +, KeyTag 64278, Signer-Name: co



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



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



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



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

Zone: certifiedspanish.co
certifiedspanish.co
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 "greasai5aleeqjh2cqq92oqk2lln52a4" between the hashed NSEC3-owner "gre85kifelcrcjj76j76sefs80i6grtb" and the hashed NextOwner "grejforn4u7ft1upsc9jkgmnvqnnqk1o". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner gre85kifelcrcjj76j76sefs80i6grtb.co., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 13.11.2020, 12:04:45 +, Signature-Inception: 14.10.2020, 11:06:46 +, KeyTag 64278, Signer-Name: co



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "131vnuv1malje6dnud9fsaqdrqcs5i91" as Owner. That's the Hash of "co" with the NextHashedOwnerName "13231jf049n78ic4unvnpgram5f58372". So that domain name is the Closest Encloser of "certifiedspanish.co". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 131vnuv1malje6dnud9fsaqdrqcs5i91.co., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 10.11.2020, 11:51:57 +, Signature-Inception: 11.10.2020, 11:19:39 +, KeyTag 64278, Signer-Name: co



The ClosestEncloser says, that "*.co" with the Hash "g85jiqjim37cr964eja38ur3huvudf10" 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 "g84uvivj5eqcrnu3v1dmmdj08qn57008" and the Next Owner "g863qhetssua4v26ktdhabfa3p00o0cf", 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 g84uvivj5eqcrnu3v1dmmdj08qn57008.co., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.11.2020, 17:41:08 +, Signature-Inception: 17.10.2020, 16:56:25 +, KeyTag 64278, Signer-Name: co

Zone: www.certifiedspanish.co
www.certifiedspanish.co
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "131vnuv1malje6dnud9fsaqdrqcs5i91" as Owner. That's the Hash of "co" with the NextHashedOwnerName "13231jf049n78ic4unvnpgram5f58372". So that domain name is the Closest Encloser of "www.certifiedspanish.co". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 131vnuv1malje6dnud9fsaqdrqcs5i91.co., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 10.11.2020, 11:51:57 +, Signature-Inception: 11.10.2020, 11:19:39 +, KeyTag 64278, Signer-Name: co



The ClosestEncloser says, that "*.co" with the Hash "g85jiqjim37cr964eja38ur3huvudf10" 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 "g84uvivj5eqcrnu3v1dmmdj08qn57008" and the Next Owner "g863qhetssua4v26ktdhabfa3p00o0cf", 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 g84uvivj5eqcrnu3v1dmmdj08qn57008.co., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.11.2020, 17:41:08 +, Signature-Inception: 17.10.2020, 16:56:25 +, KeyTag 64278, Signer-Name: co


3. Name Servers

DomainNameserverNS-IP
www.certifiedspanish.co
  ns1.cctld.co

certifiedspanish.co
  ns1.cctld.co

co
  ns1.cctld.co / dns4.frpar1


  ns2.cctld.co / dns3.defra1


  ns3.cctld.co / dns3.defra1


  ns4.cctld.co / TLD_Host2.Amsterdam_Node1


  ns5.cctld.co / TLD_Host1.Frankfurt_Node1


  ns6.cctld.co / TLD_Host1.Paris_Node1


4. SOA-Entries


Domain:co
Zone-Name:co
Primary:ns1.cctld.co
Mail:hostmaster.neustar.biz
Serial:1602969566
Refresh:900
Retry:900
Expire:604800
TTL:86400
num Entries:6


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


Domain:www.certifiedspanish.co
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 "certifiedspanish.co" is domain, public suffix is ".co", top-level-domain is ".co", top-level-domain-type is "country-code", Country is Colombia, tld-manager is ".CO Internet S.A.S.", num .co-domains preloaded: 1453 (complete: 131120)
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: ns1.cctld.co, ns2.cctld.co, ns3.cctld.co, ns4.cctld.co, ns5.cctld.co, ns6.cctld.co, 6 Name Servers included in Delegation: ns1.cctld.co, ns2.cctld.co, ns3.cctld.co, ns4.cctld.co, ns5.cctld.co, ns6.cctld.co, 6 Name Servers included in 1 Zone definitions: ns1.cctld.co, ns2.cctld.co, ns3.cctld.co, ns4.cctld.co, ns5.cctld.co, ns6.cctld.co, 1 Name Servers listed in SOA.Primary: ns1.cctld.co.
AGood: Only one SOA.Primary Name Server found.: ns1.cctld.co.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.cctld.co.
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: ns1.cctld.co: 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.cctld.co: 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.
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: 12700 milliseconds, 12.700 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
co
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=1f076d2b-43e8-4ecd-a8a1-2208779cc7f0


Last Result: https://check-your-website.server-daten.de/?q=certifiedspanish.co - 2020-10-17 23:29:47


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

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