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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
01.09.2020 09:09:47


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
stellaresultscoaching.com.ua

Name Error
yes
1
0
www.stellaresultscoaching.com.ua

Name Error
yes
1
0
*.stellaresultscoaching.com.ua
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
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 46594, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 13, KeyTag 48349, DigestType 2 and Digest 2EVt8Oqw230kIrQRByL1dy17Lx/UHUh+lWpU8QOdU8g=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ua., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.09.2020, 05:00:00 +, Signature-Inception: 01.09.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 41012, Flags 256



Public Key with Algorithm 13, KeyTag 48349, Flags 257 (SEP = Secure Entry Point)



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ua., Algorithm: 13, 1 Labels, original TTL: 36036 sec, Signature-expiration: 01.10.2020, 05:31:00 +, Signature-Inception: 01.09.2020, 05:31:00 +, KeyTag 41012, Signer-Name: ua



RRSIG-Owner ua., Algorithm: 13, 1 Labels, original TTL: 36036 sec, Signature-expiration: 01.10.2020, 05:31:00 +, Signature-Inception: 01.09.2020, 05:31:00 +, KeyTag 48349, Signer-Name: ua



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 41012 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 48349 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 48349, DigestType 2 and Digest "2EVt8Oqw230kIrQRByL1dy17Lx/UHUh+lWpU8QOdU8g=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com.ua
com.ua
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 51391, DigestType 2 and Digest CxZdHAuEgTNb+aoIttSpifqjh+UMsgASuWef2sjcxSM=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com.ua., Algorithm: 13, 2 Labels, original TTL: 36036 sec, Signature-expiration: 01.10.2020, 05:31:00 +, Signature-Inception: 01.09.2020, 05:31:00 +, KeyTag 41012, Signer-Name: ua



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 15752, Flags 256



Public Key with Algorithm 13, KeyTag 51391, Flags 257 (SEP = Secure Entry Point)



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com.ua., Algorithm: 13, 2 Labels, original TTL: 28800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 15752, Signer-Name: com.ua



RRSIG-Owner com.ua., Algorithm: 13, 2 Labels, original TTL: 28800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 51391, Signer-Name: com.ua



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 15752 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 51391 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 51391, DigestType 2 and Digest "CxZdHAuEgTNb+aoIttSpifqjh+UMsgASuWef2sjcxSM=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: stellaresultscoaching.com.ua
stellaresultscoaching.com.ua
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 "57tbb9ro790s0u5urutqf0e0qmb2u7ed" between the hashed NSEC3-owner "57rotaqooh88uac8qkas3p8icifogkb2" and the hashed NextOwner "57tehoeipsab0p87n1a41t40e5jc2p80". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 57rotaqooh88uac8qkas3p8icifogkb2.com.ua., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 15752, Signer-Name: com.ua



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "qkcpufgfo662q0iqvs6f3dgoen1k26b5" as Owner. That's the Hash of "com.ua" with the NextHashedOwnerName "qkgf6jvespphj2hedb59t0a1bk6j4car". So that domain name is the Closest Encloser of "stellaresultscoaching.com.ua". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner qkcpufgfo662q0iqvs6f3dgoen1k26b5.com.ua., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 15752, Signer-Name: com.ua



The ClosestEncloser says, that "*.com.ua" with the Hash "hv2lbifji5l066eqkb98263btrroo6km" 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 "hv28nk9i8v8nld70hk78qa261jiphuo0" and the Next Owner "hv7mlc3nqbd33nbvfvlpchhepl21afu6", 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: TXT, RRSIG Validated: RRSIG-Owner hv28nk9i8v8nld70hk78qa261jiphuo0.com.ua., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 15752, Signer-Name: com.ua

Zone: www.stellaresultscoaching.com.ua
www.stellaresultscoaching.com.ua
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "qkcpufgfo662q0iqvs6f3dgoen1k26b5" as Owner. That's the Hash of "com.ua" with the NextHashedOwnerName "qkgf6jvespphj2hedb59t0a1bk6j4car". So that domain name is the Closest Encloser of "www.stellaresultscoaching.com.ua". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner qkcpufgfo662q0iqvs6f3dgoen1k26b5.com.ua., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 15752, Signer-Name: com.ua



The ClosestEncloser says, that "*.com.ua" with the Hash "hv2lbifji5l066eqkb98263btrroo6km" 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 "hv28nk9i8v8nld70hk78qa261jiphuo0" and the Next Owner "hv7mlc3nqbd33nbvfvlpchhepl21afu6", 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: TXT, RRSIG Validated: RRSIG-Owner hv28nk9i8v8nld70hk78qa261jiphuo0.com.ua., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.10.2020, 05:45:04 +, Signature-Inception: 01.09.2020, 05:45:04 +, KeyTag 15752, Signer-Name: com.ua


3. Name Servers

DomainNameserverNS-IP
www.stellaresultscoaching.com.ua
  nix.ns.ua

stellaresultscoaching.com.ua
  nix.ns.ua

com.ua
  ba1.ns.ua
74.123.224.37
San Jose/California/United States (US) - Intuix LLC


 
2604:ee00:0:101::37
San Jose/California/United States (US) - Intuix LLC


  ho1.ns.com.ua / kyiv-c
195.47.253.3
Kyiv/Kyiv City/Ukraine (UA) - LLC "Hostmaster"


 
2001:67c:258::3
Kyiv/Kyiv City/Ukraine (UA) - LLC "Hostmaster"


  k.ns.com.ua
216.218.215.123
Santa Clara/California/United States (US) - Hurricane Electric LLC


 
2001:470:2e:46::3
San Jose/California/United States (US) - Hurricane Electric LLC


  nix.ns.ua
62.149.7.77
Kyiv/Kyiv City/Ukraine (UA) - Colocall Ltd


 
2a03:6300:1:102::3
Kyiv/Kyiv City/Ukraine (UA) - "7HEAVEN" LLC

ua
T  cd1.ns.ua


  ho1.ns.ua / kyiv-c


  in1.ns.ua


  pch.ns.ua / 1.ber.pch


4. SOA-Entries


Domain:ua
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:ua
Zone-Name:ua
Primary:in1.ns.ua
Mail:domain-master.ccTLD.UA
Serial:2020083124
Refresh:3601
Retry:3602
Expire:3024000
TTL:6666
num Entries:3


Domain:com.ua
Zone-Name:com.ua
Primary:nix.ns.ua
Mail:dnsmaster.hostmaster.ua
Serial:2008197415
Refresh:1800
Retry:900
Expire:604800
TTL:1800
num Entries:8


Domain:stellaresultscoaching.com.ua
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.stellaresultscoaching.com.ua
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 "stellaresultscoaching.com.ua" is domain, public suffix is ".com.ua", top-level-domain is ".ua", top-level-domain-type is "country-code", Country is Ukraine, tld-manager is "Hostmaster Ltd.", num .ua-domains preloaded: 345 (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

AInfo:: 5 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 5 Queries complete, 5 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ho1.ns.com.ua (195.47.253.3, 2001:67c:258::3), ba1.ns.ua (2604:ee00:0:101::37, 74.123.224.37), k.ns.com.ua (2001:470:2e:46::3, 216.218.215.123), nix.ns.ua (2a03:6300:1:102::3, 62.149.7.77)
AGood (1 - 3.0):: An average of 1.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ba1.ns.ua, ho1.ns.com.ua, k.ns.com.ua, nix.ns.ua, 4 Name Servers included in Delegation: ba1.ns.ua, ho1.ns.com.ua, k.ns.com.ua, nix.ns.ua, 4 Name Servers included in 1 Zone definitions: ba1.ns.ua, ho1.ns.com.ua, k.ns.com.ua, nix.ns.ua, 1 Name Servers listed in SOA.Primary: nix.ns.ua.
AGood: Only one SOA.Primary Name Server found.: nix.ns.ua.
AGood: SOA.Primary Name Server included in the delegation set.: nix.ns.ua.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 195., 216., 62., 74., 4 different subnets (first two Bytes): 195.47., 216.218., 62.149., 74.123., 4 different subnets (first three Bytes): 195.47.253., 216.218.215., 62.149.7., 74.123.224.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2604:, 2a03:, 4 different subnets (first two blocks): 2001:0470:, 2001:067c:, 2604:ee00:, 2a03:6300:, 4 different subnets (first three blocks): 2001:0470:002e:, 2001:067c:0258:, 2604:ee00:0000:, 2a03:6300:0001:, 4 different subnets (first four blocks): 2001:0470:002e:0046:, 2001:067c:0258:0000:, 2604:ee00:0000:0101:, 2a03:6300:0001:0102:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
XNameserver Timeout checking Echo Capitalization: cd1.ns.ua
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
XNameserver Timeout checking EDNS512: cd1.ns.ua
Nameserver doesn't pass all EDNS-Checks: cd1.ns.ua: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: nix.ns.ua: 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: nix.ns.ua: 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: 113610 milliseconds, 113.610 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: ba1.ns.ua, ho1.ns.com.ua, k.ns.com.ua, nix.ns.ua

QNr.DomainTypeNS used
1
ua
NS
b.root-servers.net (2001:500:200::b)

Answer: cd1.ns.ua, ho1.ns.ua, in1.ns.ua, pch.ns.ua
2
ba1.ns.ua
NS
cd1.ns.ua (2001:678:4::9)

Answer: in1.ns.ua
3
ho1.ns.com.ua: 195.47.253.3, 2001:67c:258::3
NS
cd1.ns.ua (2001:678:4::9)

Answer: ba1.ns.ua
2604:ee00:0:101::37, 74.123.224.37

Answer: k.ns.com.ua
2001:470:2e:46::3, 216.218.215.123

Answer: nix.ns.ua
2a03:6300:1:102::3, 62.149.7.77
4
ba1.ns.ua: 74.123.224.37
A
in1.ns.ua (2604:ee00:0:101::40)
5
ba1.ns.ua: 2604:ee00:0:101::37
AAAA
in1.ns.ua (2604:ee00:0:101::40)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
com.ua
0

no CAA entry found
1
0
ua
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=b1392810-b53c-48df-ae23-34e9ec341b81


Last Result: https://check-your-website.server-daten.de/?q=stellaresultscoaching.com.ua - 2020-09-01 09:09: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=stellaresultscoaching.com.ua" target="_blank">Check this Site: stellaresultscoaching.com.ua</a>