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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
23.02.2021 11:41:46


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bbb.km.uz

Name Error
yes
1
0
www.bbb.km.uz

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: uz
uz
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "uz" and the NextOwner "va". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found




Zone: km.uz
km.uz
0 DS RR in the parent zone found

Zone: bbb.km.uz
bbb.km.uz
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.bbb.km.uz
www.bbb.km.uz
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.bbb.km.uz
  rdns1.ahost.uz

bbb.km.uz
  rdns1.ahost.uz


  rdns2.ahost.uz / rdns2.ahost.uz
116.202.82.237
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH

uz
T  ns.uz


  ns1.uz


  ns2.uz


  ns3.uz


  ns4.uz


  ns5.uz


  ns6.uz


  ns7.uz


4. SOA-Entries


Domain:uz
Zone-Name:uz
Primary:ns.uz
Mail:hostmaster.cctld.uz
Serial:2021022314
Refresh:3600
Retry:900
Expire:5184000
TTL:14400
num Entries:8


Domain:bbb.km.uz
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:bbb.km.uz
Zone-Name:km.uz
Primary:rdns1.ahost.uz
Mail:support.ahost.uz
Serial:2021021600
Refresh:3600
Retry:1800
Expire:1209600
TTL:86400
num Entries:1


Domain:www.bbb.km.uz
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 "bbb.km.uz" is subdomain, public suffix is ".uz", top-level-domain is ".uz", top-level-domain-type is "country-code", Country is Uzbekistan, tld-manager is "Single Integrator for Creation and Support of State Information Systems UZINFOCOM", num .uz-domains preloaded: 18 (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.
XFatal error: Nameserver doesn't support TCP connection: rdns2.ahost.uz / 116.202.82.237: NXDOMAIN

2. DNS- and NameServer - Checks

A
A
AInfo:: 0 different Name Servers found: , 0 Name Servers included in Delegation: , 0 Name Servers included in 0 Zone definitions: , 0 Name Servers listed in SOA.Primary: .
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
XNameserver Timeout checking Echo Capitalization: ns.uz
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
XNameserver Timeout checking EDNS512: ns.uz
Nameserver doesn't pass all EDNS-Checks: ns.uz: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns5.uz: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: rdns1.ahost.uz: 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: rdns1.ahost.uz: 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: 131517 milliseconds, 131.517 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
bbb.km.uz
-3

Name Error - The domain name does not exist
1
0
uz
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bbb.km.uz

Name Error - The domain name does not exist
1
0
_acme-challenge.bbb.km.uz

Name Error - The domain name does not exist
1
0
_acme-challenge.bbb.km.uz.bbb.km.uz

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=3aad55e0-021a-4484-9da3-0cf2e9b2e405


Last Result: https://check-your-website.server-daten.de/?q=bbb.km.uz - 2021-02-23 11:41:46


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

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